Publish and share releases

Draft → publish → share

A release contains a version, title, notes, and selected downloadable files. Upload creates a private draft. Publish version makes a verified release eligible for sharing. Enable release sharing creates an unlisted URL that follows future published versions.

A Git push or tag does not create a release. GitHub releases and the official CLI download store are separate from repository release records. Build output stays in a draft until you publish it.

Publish from the website

1. Open your repository → Releases → New release.
2. Enter a unique version, title, and notes; select the files intended for recipients.
3. Upload the draft and wait for every artifact to be verified. Up to 20 files are supported, each from 1 byte to 512 MiB.
4. Review the draft and downloads, then click Publish version.
5. Enable release sharing and open the download page. Copy its link for recipients.

Publish from the CLI

Repeat --file for more artifacts. Omit --publish to keep a draft. Inside a clone, --repo can be omitted.

orbitgit release create 1.0.0 --repo your-user/my-app \
  --title "My app 1.0" --notes-file RELEASE-NOTES.md \
  --file dist/app-linux.tar.gz --file dist/app-macos.zip \
  --publish --share
orbitgit release list
orbitgit release upload RELEASE_ID --file dist/app.zip
orbitgit release publish RELEASE_ID
orbitgit release share

What sharing grants

Anyone with the URL can read published titles, versions, notes, checksums, and files. Source trees, commits, vault secrets, and Git access are not granted. Archives expose everything inside them; inspect their contents before publishing.

Published releases and completed artifacts are immutable. Use a new version for changed files. Revoke link and update feed disables the page, feed, and future downloads. Reenabling generates a new link; already downloaded files cannot be recalled.

orbitgit release revoke
orbitgit release delete RELEASE_ID --yes

Why a release is missing

An empty Releases tab means no repository release record exists. Git pushes, GitHub releases, and tags are separate. Upload a release or use a build’s draft.

A draft visible in the repository is absent from the shared page until you publish it. Sharing never publishes drafts automatically. A disabled Publish button means files are absent or not fully verified.

The tab refreshes periodically and on focus. Check the selected account and repository. Failed uploads stay private; delete and retry the incomplete draft or resume its chunks through the API.

Automatic update checks

The same share URL has a stable latest.json feed. Publishing a new release updates it without changing the link.