name: Dev: Release a patch version about: ONLY USED BY MAINTAINERS. title: "Release [VERSION]"
_This is generated from the patch release template._
On the release branch:
main
branch by checking the patch milestone.main
branch to include entries for the current patch release.On the release branch:
0.12.0
-> 0.12.1
.v0.12.0-rc.1
, v0.12.0-rc.2
) to ensure Docker workflow succeeds. Make sure the tag is created on the release branch.
[ ] 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 image tag for the current release to be created automatically on both Docker Hub and GitHub Container registry.
[ ] Update Docker image tag for the minor release <MAJOR>.<MINOR>
on both Docker Hub and GitHub Container registry.
[ ] Compile and pack binaries (all prefixed with gogs_<MAJOR>.<MINOR>.<PATCH>_
, e.g. gogs_0.12.0_
):
darwin_amd64.zip
, darwin_arm64.zip
linux_386.tar.gz
, linux_386.zip
, linux_amd64.tar.gz
, linux_amd64.zip
linux_armv7.tar.gz
, linux_armv7.zip
, linux_armv8.tar.gz
, linux_armv8.zip
windows_amd64.zip
, windows_amd64_mws.zip
[ ] Generate SHA256 checksum for all binaries to the file checksum_sha256.txt
.
[ ] Upload all binaries and checksum_sha256.txt
to:
[ ] Update content of Install from binary.
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.
[ ] Update the repository mirror on Gitee.
[ ] Create a new release announcement in Discussions.
[ ] Send a tweet on the official Twitter account for the patch release.
[ ] Close the patch milestone.