ci: release#172
Open
mixie-bot[bot] wants to merge 1 commit into
Open
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
atproto-pds | 49482c0 | May 24 2026, 06:56 AM |
commit: |
d0a7af5 to
49482c0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@getcirrus/pds@0.16.0
Minor Changes
#171
bf2f857Thanks @ascorbic! - The firehose now emits the sync 1.1 message shape, matching what the bsky.network relay and other AT Protocol consumers expect. Existing subscribers will start seeing new fields and new event types; nothing has to change on the consumer side, but the warnings some relays were logging against Cirrus hosts (notablymissing prevData field) will stop.What changed on the wire:
#commitmessages now includeprevData(the prior commit's MST root CID), so relays can verify each commit inductively without re-fetching the repo. The CAR slice now also carries the MST covering-proof blocks needed for that verification.ops[]entry on update and delete now includesprev, the previous CID of the touched record. Creates omit it as before.tooBigis alwaysfalse. It was previously set based on payload size, which never matched the field's meaning under sync 1.1.#accountevents are emitted on activation and deactivation, so relays learn about account status changes without polling. Deactivation reportsstatus: "deactivated"; activation reportsactive: truewith no status.#syncevents are emitted on activation (after migration or initial setup), giving relays the current commit block without a diff.#identityevents now allow thehandlefield to be omitted, per spec.#infoframe withname: "OutdatedCursor"is sent when a client connects with a cursor older than the retained event window. The stream continues from the oldest available event instead of disconnecting.applyWritesrejects calls with more than 200 operations, matching the spec cap.#168
71b988eThanks @simnaut! - Implementcom.atproto.sync.getLatestCommit.This sync XRPC endpoint was previously unimplemented, so requests fell through to the XRPC proxy and returned
501 MethodNotImplemented. Relays callgetLatestCommitduring their crawl bootstrap, so a freshly created repo could never be indexed by a freshrequestCrawl. The endpoint now returns the repo's head commit as{ cid, rev }(sourced from the samerpcGetRepoStatusdata used bygetRepoStatus/listRepos).