USEFULL
/
gogs
mirror of https://github.com/gogs/gogs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
gogs/.github/ISSUE_TEMPLATE/dev_release_patch_version.md

2.8 KiB
Raw Blame History

name: Dev: Release a patch version about: ONLY USED BY MAINTAINERS. title: "Release [VERSION]" labels: 📸 release

Before release

On the release branch:

  • Make sure all commits are cherry-picked from the main branch by checking the patch milestone.
  • Update CHANGELOG to include entries for the current patch release, e.g. git log v0.12.1...HEAD --pretty=format:'- [ ] %H %s' --reverse:
    • link to the commit

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 a new GitHub release with entries from CHANGELOG for the current patch release and all previous releases with same minor version. 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>, e.g. 0.12 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_):
    • macOS: darwin_amd64.zip, darwin_arm64.zip
    • Linux: linux_386.tar.gz, linux_386.zip, linux_amd64.tar.gz, linux_amd64.zip
    • ARM: linux_armv7.tar.gz, linux_armv7.zip, linux_armv8.tar.gz, linux_armv8.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:

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.
  • Update the repository mirror on Gitee.
  • Reply to the release topic for the minor release in Discussions.
  • Close the patch milestone.