Published to pgh
Trees recorded in the pgh release registry by pgh publish. These are
installed with pgh app install, not downloaded — there is no file to
fetch. Separate from the build artifacts below; the two are not the same namespace
and a repo may have either, both, or neither.
Nothing published to pgh under the name atproto-did-peer.
Build artifacts
Files produced by this repo's .pear-git/ci.yaml and served over HTTP.
⚠ These are node-local — each daemon serves only what it built
itself, so a peer that did not run the build has nothing here.
Channels
No channels pinned yet. Publish a release with a channel, or promote an existing version.
0 versions
No releases published yet. Build artifacts land here once the publish-release RPC runs (via CLI, post-push hook, or the HTTP upload endpoint).
Build a release
Runs this repo's .pear-git/ci.yaml against a branch or tag, collects the listed artifacts, and publishes the result. If the ref has channel rules in the yaml (e.g. tags → production), the channel is set automatically — otherwise leave it blank for an unpinned version.
Garbage collection
Default policy keeps every channel-pinned version + the 3 newest unpinned. Older unpinned versions become GC candidates.