gogs/docs/dev/release/issue_template_patch_release.md

Before release

On develop branch:

• Update CHANGELOG to include entries for the current patch release.

During release

On release branch:

• Cherry-pick commits from develop branch:
  • link to the commit
• Wait for GitHub Actions to complete and no failed jobs.
• Update the hard-coded version to the current release, e.g. 0.12.0 -> 0.12.1.
• Publish a new GitHub release 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 a new Docker Hub tag for the current release to be created automatically.

• [ ] Update Docker image tag for the minor release <MAJOR>.<MINOR>, e.g. 0.12.

• [ ] Compile and pack binaries (all prefixed with gogs_<MAJOR>.<MINOR>.<PATCH>_, e.g. gogs_0.12.0_):

  • macOS: darwin_amd64.zip
  • Linux: linux_386.tar.gz, linux_386.zip, linux_amd64.tar.gz, linux_amd64.zip
  • ARM: linux_armv7.tar.gz, linux_armv7.zip
  • Windows: windows_amd64.zip, windows_amd64_mws.zip

• [ ] Generate SHA256 checksum for all binaries to the file checksum_sha256.txt.

• [ ] Upload all binaries to:

  • GitHub release
  • https://dl.gogs.io (also upload checksum_sha256.txt)

• [ ] Build, push and tag a new Docker image for ARM to Docker Hub.

After release

On develop branch:

• Update the repository mirror on Gitee.
• Reply to the release topic for the minor release on Gogs Discussion.