OverviewFilesCommitsIssuesDocsReleasesPeers

← favela-android / 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.
5 of 5 entries are not stored on this forge and are hidden. The registry is append-only; the tree store is garbage-collected, so older entries outlive their bytes. Another peer may still hold them. show all 5
Nothing published to pgh under the name favela-android.

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.

5 versions

VersionBuiltSizeArtifactsActions
master-640023e 29d ago 201.3 MiB favela-android.apk 160.5 MiB · worklet.bundle 40.4 MiB · tree.json 289 B · apk.tree.json 294 B · build.log 358.4 KiB
master-aa00f8a 29d ago 201.3 MiB favela-android.apk 160.5 MiB · worklet.bundle 40.4 MiB · tree.json 289 B · apk.tree.json 294 B · build.log 358.5 KiB
master-8d988ca 1mo ago 201.3 MiB favela-android.apk 160.5 MiB · worklet.bundle 40.4 MiB · tree.json 289 B · apk.tree.json 294 B · build.log 355.2 KiB
master-9e8aa66 1mo ago 201.2 MiB favela-android.apk 160.5 MiB · worklet.bundle 40.4 MiB · tree.json 289 B · apk.tree.json 294 B · build.log 355.2 KiB
master-9d18502 1mo ago 201.2 MiB favela-android.apk 160.5 MiB · worklet.bundle 40.4 MiB · tree.json 289 B · apk.tree.json 294 B · build.log 355.2 KiB

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.