Release Your Software
Today, we’re excited to announce Releases, a workflow for shipping software to end users. Releases are first-class objects with changelogs and binary assets that present a full project history beyond…
Today, we’re excited to announce Releases, a workflow for shipping
software to end users. Releases are first-class objects with changelogs
and binary assets that present a full project history beyond Git artifacts.
They’re accessible from a repository’s homepage:
Releases are accompanied by release notes and links to download the software
or source code.
Following the conventions of many Git projects, releases are tied to Git tags.
You can use an existing tag, or let releases create the tag when it’s published.
We recommend projects use Semantic Versioning, but it is
not required.
Creating Releases
As a repository collaborator, you can draft up a changelog in a release’s notes.
Any non-production releases (alphas, betas, release candidates) can be
identified through the pre-release checkbox.
You can also attach binary assets (such as compiled executables,
minified scripts, documentation) to a release. Once published, the
release details and assets are available to anyone that can view the repository.
Happy shipping!
Written by
Related posts
GitHub Availability Report: September 2024
In September, we experienced three incidents that resulted in degraded performance across GitHub services.
Code referencing now generally available in GitHub Copilot and with Microsoft Azure AI
Announcing the general availability of code referencing in GitHub Copilot and Microsoft Azure AI, allowing developers to permit code suggestions containing public code matches while receiving detailed information about the match.
The nuances and challenges of moderating a code collaboration platform
Sharing the latest data update to our Transparency Center alongside a new research article on what makes moderating a code collaboration platform unique.