OverviewFilesCommitsIssuesDocsReleasesPeers

← favela-bridge / releases

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.
11 of 11 entries are not stored on this forge and are shown below, marked. The registry is append-only; the tree store is garbage-collected, so older entries outlive their bytes. Another peer may still hold them. show only what this forge serves
VersionPublishedDepsTreeInstall
0.0.12 bare not stored here 1mo ago 304 25ba97434575 unavailable from this forge
0.0.11 bare not stored here 1mo ago 304 6fbdd1258ae3 unavailable from this forge
0.0.10 bare not stored here 1mo ago 304 91523f94de17 unavailable from this forge
0.0.9 bare not stored here 1mo ago 304 4b50aeffe6a1 unavailable from this forge
0.0.8 bare not stored here 1mo ago 304 ae5f94d4ca4a unavailable from this forge
0.0.7 bare not stored here 1mo ago 304 d0caf910b7b7 unavailable from this forge
0.0.6 bare not stored here 1mo ago 304 cab96cad4e36 unavailable from this forge
0.0.5 bare not stored here 1mo ago 304 da2414349c19 unavailable from this forge
0.0.3 bare not stored here 1mo ago 301 e9a49b1b63f7 unavailable from this forge
0.0.2 bare not stored here 1mo ago 301 664a0b81dd1e unavailable from this forge
0.0.1 node not stored here 1mo ago 301 6a2b0bce00ba unavailable from this forge

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.