gogs/.github/ISSUE_TEMPLATE/dev_release_patch_version.md

---

name: "Dev: Release a patch version" about: ONLY USED BY MAINTAINERS. assignees: "unknwon" title: "Release [VERSION]"

labels: 📸 release

_This is generated from the patch release template._

Before release

On the release branch:

• Make sure all commits are cherry-picked from the main branch by checking the patch milestone.
  • Run task build for every cherry-picked commit to make sure there is no compilation error.
• Update CHANGELOG on the main branch to include entries for the current patch release.

During release

On the release branch:

• Update the hard-coded version to the current release, e.g. 0.12.0 -> 0.12.1.
• Wait for GitHub Actions to complete and no failed jobs.
• Publish new RC releases in GitHub release (e.g. v0.12.0-rc.1, v0.12.0-rc.2) ⚠️ on the release branch ⚠️ and ensure Docker workflow succeeds.
  • Pull down the Docker image and run through application setup to make sure nothing blows up.
  • Download one of the release archives and run through application setup to make sure nothing blows up.
• Publish a new GitHub release ⚠️ on the release branch ⚠️ with entries from CHANGELOG for the current patch release and all previous releases with same minor version.

• [ ] Update all previous GitHub releases with same minor version with the warning:

  **ℹ️ Heads up! There is a new patch release [0.12.1](https://github.com/gogs/gogs/releases/tag/v0.12.1) available, we recommend directly installing or upgrading to that version.**
  

• [ ] Wait for new image tags for the current release to be created automatically on both Docker Hub and GitHub Container registry.

  • Pull down the Docker image and run through application setup to make sure nothing blows up.

• [ ] Download all release archives and generate SHA256 checksum for all binaries to the file checksum_sha256.txt.

• [ ] Upload all archives and checksum_sha256.txt to https://dl.gogs.io.

After release

On the main branch:

• [ ] Post the following message on issues that are included in the patch milestone:

  The <MAJOR>.<MINOR>.<PATCH> has been released that includes the patch of the reported issue.
  

• [ ] Create a new release announcement in Discussions.

• [ ] Send a tweet on the official Twitter account for the patch release.

• [ ] Close the milestone for the patch release.

• [ ] After 14 days, publish GitHub security advisories for security patches included in the release.