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
We need a European Sovereign Tech Fund
Open source software is critical infrastructure, but it’s underfunded. With a new feasibility study, GitHub’s developer policy team is building a coalition of policymakers and industry to close the maintenance funding gap.
GitHub Availability Report: June 2025
In June, we experienced three incidents that resulted in degraded performance across GitHub services.
From pair to peer programmer: Our vision for agentic workflows in GitHub Copilot
AI agents in GitHub Copilot don’t just assist developers but actively solve problems through multi-step reasoning and execution. Here’s what that means.