Skip to content

ci: release#172

Open
mixie-bot[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

ci: release#172
mixie-bot[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@mixie-bot
Copy link
Copy Markdown
Contributor

@mixie-bot mixie-bot Bot commented May 24, 2026

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 bf2f857 Thanks @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 (notably missing prevData field) will stop.

    What changed on the wire:

    • #commit messages now include prevData (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.
    • Each ops[] entry on update and delete now includes prev, the previous CID of the touched record. Creates omit it as before.
    • tooBig is always false. It was previously set based on payload size, which never matched the field's meaning under sync 1.1.
    • New #account events are emitted on activation and deactivation, so relays learn about account status changes without polling. Deactivation reports status: "deactivated"; activation reports active: true with no status.
    • New #sync events are emitted on activation (after migration or initial setup), giving relays the current commit block without a diff.
    • #identity events now allow the handle field to be omitted, per spec.
    • A #info frame with name: "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.
    • applyWrites rejects calls with more than 200 operations, matching the spec cap.
  • #168 71b988e Thanks @simnaut! - Implement com.atproto.sync.getLatestCommit.

    This sync XRPC endpoint was previously unimplemented, so requests fell through to the XRPC proxy and returned 501 MethodNotImplemented. Relays call getLatestCommit during their crawl bootstrap, so a freshly created repo could never be indexed by a fresh requestCrawl. The endpoint now returns the repo's head commit as { cid, rev } (sourced from the same rpcGetRepoStatus data used by getRepoStatus/listRepos).

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented May 24, 2026

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
atproto-pds 49482c0 May 24 2026, 06:56 AM

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 24, 2026

Open in StackBlitz

npm i https://pkg.pr.new/create-pds@172
npm i https://pkg.pr.new/@getcirrus/oauth-provider@172
npm i https://pkg.pr.new/@getcirrus/pds@172

commit: 49482c0

@mixie-bot mixie-bot Bot force-pushed the changeset-release/main branch from d0a7af5 to 49482c0 Compare May 24, 2026 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants