OverviewFilesCommitsIssuesDocsReleasesPeers

atproto-bridge commits / 6bccb1e

0.9.29: pick up atproto-did-peer 0.2.4 (front a STATELESS peer)
0.2.3 made repoKey optional in DidPeer.onAnnounce, but DidPeerRouter._onAnnounce gated on it too and dispatches FIRST, so a peer running the stateless virtual device (serve-membrane projectRepoCore:false) had its announce dropped before it reached the DidPeer. Verified live: tabertron's wj62 flipped stateless, stayed healthy and kept serving, but this membrane showed its front live=false and never re-fronted it. 0.2.4 fixes the router gate and additionally drops a now-frozen repo-core replica when a peer announces repoKey:null, so getRepo falls through to the verified get-repo-car derive path instead of failing its data-root assertion forever. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
6bccb1ee8db259f6a14de0b3391ff2af56c1b650
by plankatron <fleeky@gmail.com> · 2026-07-26T23:59:25.000Z

Changed files (1) +1 -1

package.json +1 -1
……@@ -1,6 +1,6 @@
11{
22 "name": "atproto-bridge",
3 "version": "0.9.28",
3 "version": "0.9.29",
44 "description": "Stateless keyless atproto MEMBRANE — fronts self-custody hyper-proto-peers to bluesky over HTTP/WS, holds no keys and never signs. Bare-runnable. Deploy root / flat closure over the identity+repo+store+pds packages.",
55 "type": "module",
66 "main": "index.js",