Release: Publish Gitea 1.23.4

[lunny]

1.23.4

• Check cowdin sync
• Prepare a new changelog (there are a lot of new changes) and update CHANGELOG.md
• Close milestone of 1.23.4
• Release 1.23.4 from release/v1.23 branch
  • Generate changelog_1.23.4.md from merged CHANGELOG.md
  • Frontend changelog to main branch Add missed changelogs #33649
  • Tag 1.23.4 with git tag -s -f changelog_1.23.4.md v1.23.4 and Push to Github
  • Wait for the release created and check whether the release artifacts generated
    • Check whether Github release attachments are generated and normal
    • Check whether the binaries generated under https://dl.gitea.com/gitea/1.23.4/ and normal
    • Check whether docker images are generated https://hub.docker.com/r/gitea/gitea/tags?page=&page_size=&ordering=&name=1.23.4
  • If the release does work then make it out of draft so that it's public for everyone.
• Official packages updated
  • Homebrew gitea 1.23.4 Homebrew/homebrew-core#208233
  • Snap https://snapcraft.io/gitea
  • Helm Chart https://gitea.com/gitea/helm-chart/pulls/797
  • Terraform https://gitea.com/gitea/terraform-provider-gitea/pulls/97
• Update "version.json" to 1.23.4
• Update documentation's latest stable version to 1.23.4
• Confirm blog is ready and merge
• Announce the 1.23.4 release.

[wxiaoguang]

The CHANGELOG.md on main branch is out-dated for long time again.

No idea why there are always things forgotten again and again.

[lunny]

The frontport of changelog task item added and #33649 is sent.

[wxiaoguang]

I still think it should either:

• Add more todo/check list items
• Simplify the CHANGELOG.md (just link to somewhere else) and only use one mechanism to maintain and display

And reiterate my previous comment: #32924 (comment)

I think there should be a document recording all tasks need to be checked/done regularly and when they were done last time, I could only guess some:

1. dependency update
    * language (golang, nodejs)
    * go, js, and other packages
    * docker images
2. crowdin sync
3. gitea.com / demo update
4. release packages: snap, homebrew, etc

[lunny]

1. dependency update
   language (golang, nodejs)
   go, js, and other packages
   docker images

What did you mean

2. crowdin sync

Did you mean backport languages changes from main branch? The crowdin data currently will only be sync to main branch.

3. gitea.com / demo update

Since both these two instances never follow a fixed release, should we still need to check them?

4. release packages: snap, homebrew, etc

Added.

[wxiaoguang]

1. dependency update
   language (golang, nodejs)
   go, js, and other packages
   docker images

What did you mean

I mean update dependency

I mean

I think there should be a document recording all tasks need to be checked/done REGULARY