Releases
A repository's Releases tab lists published releases you can access. Release management can be disabled by the deployment administrator even when published releases remain readable.
Download a release
Choose a published release and inspect its tag, target commit, notes, and available assets. Use the download links shown on that release. Private repository downloads require permission; copying a link does not make the asset public.
When the publisher provides checksums or verification instructions, follow them before installing a binary. An uploaded file is not automatically a signed or independently qualified release.
Prepare a release
You need repository write permission and enabled release management. First push the intended Git tag to the repository. Creating or publishing release metadata does not create or move the tag for you.
- Open Releases and choose the new release action when it is available.
- Select an existing tag and enter a title and release notes.
- Save the draft, review its target commit, and attach assets if the deployment supports them.
- Publish after completing your repository's review and release requirements.
Drafts are visible to authorized writers. Publication makes the release available according to repository visibility. Generated notes are a starting point for review; check that they describe the actual changes and include relevant migration or compatibility instructions.
Change a release
Authorized writers can edit metadata and use the available archive or restore actions. These actions do not replace a Git tag or change its target. If a tag or storage route changed while publication was being prepared, refresh the release and verify the target again before retrying.
Repository releases and the platform's own desktop or CLI release channels are separate. For those clients, use Desktop and mobile and the Download page.