This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2020-01-22. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Creating releases

You can create a release to provide packaged software, release notes, and binary files for other people to use.

In this article

You can publish a GitHub Action from a specific release in GitHub Marketplace. For more information, see "Publishing an action in the GitHub Marketplace" in the GitHub Developer documentation.

Note: Only users with write access to the repository can view drafts of releases. For more information, see:

  1. On GitHub Enterprise, navigate to the main page of the repository.

  2. Under your repository name, click Releases.

    Releases tab

  3. Click Draft a new release.

    Releases draft button

  4. Type a version number for your release. Versions are based on Git tags. We recommend naming tags that fit within semantic versioning.

    Releases tagged version

  5. Use the drop-down menu, and select the branch that contains the project you want to release.

    Releases tagged branch

  6. Type a title and description for your release.

    Releases description

  7. Optionally, to include binary files such as compiled programs in your release, drag and drop or select files manually in the binaries box.

    Providing a DMG with the Release

  8. If the release is unstable, to notify users that the release is not ready for production, select This is a pre-release.

    Checkbox to mark a release as prerelease

  9. If you're ready to publicize your release, click Publish release. To work on the release later, click Save draft.

    Publish release and Draft release buttons

Automatically creating releases

If you'd like to automatically create releases from the command line or in a script, see "Releases" in the GitHub Developer documentation.

Further reading

Ask a human

Can't find what you're looking for?

Contact us