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: October 2025
In October, we experienced four incidents that resulted in degraded performance across GitHub services.
TypeScript, Python, and the AI feedback loop changing software development
An interview with the leader of GitHub Next, Idan Gazit, on TypeScript, Python, and what comes next.
What 986 million code pushes say about the developer workflow in 2025
Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.