Skip to main content
We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation.
 
2022-11-28 (latest)

 

Managing releases in a repository

In this article

You can create releases to bundle and deliver iterations of a project to users.

Who can use this feature

Repository collaborators and people with write access to a repository can create, edit, and delete a release.

About release management

You can create new releases with release notes, @mentions of contributors, and links to binary files, as well as edit or delete existing releases. You can also create, modify, and delete releases by using the Releases API. For more information, see "Releases" in the REST API documentation.

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

You can choose whether Git Large File Storage (Git LFS) objects are included in the ZIP files and tarballs that GitHub Enterprise Cloud creates for each release. For more information, see "Managing Git LFS objects in archives of your repository."

Creating a release

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

  2. À direita da lista de arquivos, clique em Versões. Seção de versões na barra lateral à direita

  3. Click Draft a new release.

    Releases draft button

  4. Click Choose a tag, type a version number for your release, and press Enter. Alternatively, select an existing tag.

    Enter a tag

  5. If you are creating a new tag, click Create new tag.

    Screenshot of confirming you want to create a new tag

  6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.

    Screenshot of dropdown to choose a branch

  7. Opcionalmente, no canto superior direito da caixa de texto de descrição, selecione o menu suspenso Tag anterior e clique na tag que identifica a versão anterior. Captura de tela mostrando como selecionar uma tag para identificar a versão anterior

  8. Type a title and description for your release. If you @mention anyone in the description, the published release will include a Contributors section with an avatar list of all the mentioned users. Alternatively, you can automatically generate your release notes by clicking Generate release notes.

    Screenshot of the releases description

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

    Animated GIF of Providing a DMG with the Release

  10. To notify users that the release is not ready for production and may be unstable, select This is a pre-release.

    Screenshot of the checkbox to mark a release as prerelease

  11. Optionally, you can select Set as latest release. If you do not select this option, the latest release label will automatically be assigned based on semantic versioning.

    Screenshot of the checkbox to mark a release as the latest release

  12. Optionally, if GitHub Discussions are enabled in the repository, select Create a discussion for this release, then select the Category drop-down menu and click a category for the release discussion.

    Screenshot of the checkbox to create a release discussion and drop-down menu to choose a category

  13. 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 You can then view your published or draft releases in the releases feed for your repository. For more information, see "Screenshot of your repository's releases and tags."

    Published release with @mentioned contributors

Para saber mais sobre a GitHub CLI, confira "Sobre a GitHub CLI".

  1. To create a release, use the gh release create subcommand. Replace tag with the desired tag for the release.

    gh release create TAG

  2. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see the GitHub CLI manual. For example, this command creates a prerelease with the specified title and notes.

    gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a beta release" --prerelease

If you @mention any GitHub Enterprise Cloud users in the notes, the published release on GitHub.com will include a Contributors section with an avatar list of all the mentioned users.

Editing a release

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

  2. À direita da lista de arquivos, clique em Versões. Seção de versões na barra lateral à direita

  3. On the right side of the page, next to the release you want to edit, click . Edit a release

  4. Edit the details for the release in the form, then click Update release. If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the Contributors section of the release. Update a release

Releases cannot currently be edited with GitHub CLI.

Deleting a release

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

  2. À direita da lista de arquivos, clique em Versões. Seção de versões na barra lateral à direita

  3. On the right side of the page, next to the release you want to delete, click . Delete a release

  4. Click Delete this release. Confirm delete release

  1. To delete a release, use the gh release delete subcommand. Replace tag with the tag of the release to delete. Use the -y flag to skip confirmation.

    gh release delete TAG -y