Release [VERSION]

[Aliqateebah]

This is generated from the minor release template.

Before release

On the main branch:

• [x] Close stale issues with the label status: needs feedback.
• [x] Sync locales from Crowdin.
• [x] Update CHANGELOG to include entries for the current minor release.
• [x] Cut a new release branch release/<MAJOR>.<MINOR>, e.g. release/0.12.

During release

On the release branch:

• [x] Update the hard-coded version to the current release, e.g. 0.12.0+dev -> 0.12.0.
• [x] Wait for GitHub Actions to complete and no failed jobs.
• [x] Publish new RC releases (e.g. 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.
  • Pull down the Docker image and run through application setup to make sure nothing blows up.
• [x] Publish a new GitHub release with entries from CHANGELOG for the current minor release. Make sure the tag is created on the release branch.
• [x] Wait for a new image tag for the current release to be created automatically on both Docker Hub and GitHub Container registry.
• [x] Push a new Docker image tag as <MAJOR>.<MINOR> to both Docker Hub and GitHub Container registry, e.g.:
• [x] Compile and pack binaries (all prefixed with gogs_<MAJOR>.<MINOR>.<PATCH>_, e.g. gogs_0.12.0_):
  • [x] macOS: darwin_amd64.zip, darwin_arm64.zip
  • [x] Linux: linux_386.tar.gz, linux_386.zip, linux_amd64.tar.gz, linux_amd64.zip
  • [x] ARM: linux_armv7.tar.gz, linux_armv7.zip, linux_armv8.tar.gz, linux_armv8.zip
  • [x] Windows: windows_amd64.zip, windows_amd64_mws.zip
• [x] Generate SHA256 checksum for all binaries to the file checksum_sha256.txt.
• [x] Upload all binaries and checksum_sha256.txt to:
  • [x] GitHub release
  • [x] https://dl.gogs.io
• [x] Update content of Install from binary.

After release

On the main branch:

• [x] Publish GitHub security advisories for security patches included in the release.
• [x] Update the repository mirror on Gitee.
• [x] Create a new release announcement in Discussions.
• [x] Send a tweet on the official Twitter account for the minor release.
• [x] Publish a new release article on OSChina.
• [x] Close the minor milestone.
• [x] Bump the hard-coded version to the new develop version, e.g. 0.12.0+dev -> 0.13.0+dev.
• [x] Run task legacy to identify deprecated code that is aimed to be removed in current develop version.