Release of `v23.0.0`

[systay]

Note

This release is scheduled for Mon 3 Nov 2025.
The release of vitess-operator v2.16.0 is also planned.
Release team: @vitessio/release

Important

Please do not edit the content of the Issue's body manually.
The vitess-releaser tool is managing and handling this issue.
You can however click on the check boxes to mark them as done/not done, and write comments.

Prerequisites (~2 weeks before)

• General prerequisites.
  • Be part of the Release team in the vitessio GitHub organization, here.
  • Be an admin of the planetscale/vitess-operator repository.
  • Have access to Vitess' Java repository and have it working locally, guide here.
  • Have vitessio/vitess and planetscale/vitess-operator cloned in the same parent directory.
• Notify the community on Slack.
• Make sure the release notes summary is prepared and clean.
• Make sure important Pull Requests are merged, list below.
  • fix sqlSelectLimit propagating to subqueries #18716
  • copy_state: use a mediumblob instead of a smaller varbinary for lastpk #18852
  • [release-23.0] ci: DRY up MySQL Setup (#18815) #18837
  • [release-23.0] ci: extract os tuning (#18824) #18827
  • [Query Throttler]Gracefully handle config file not found scenario #18735
  • vtorc: wait for ackers before solving PrimarySemiSyncMustBeSet problem #18732
  • BuiltinBackupEngine: Retry file close and fail backup when we cannot #18848
  • [release-23.0] Fix flaky tests (#18835) #18839
  • Upgrade examples/operator.yaml with the new version #18769
  • [release-23.0] copy_state: use a mediumblob instead of a smaller varbinary for lastpk (#18852) #18859
  • [release-23.0] Release of v23.0.0 #18856
  • [release-23.0] BuiltinBackupEngine: Retry file close and fail backup when we cannot (#18848) #18862
  • golangci-lint: add sqlclosecheck linter and fixes #18844
  • [release-23.0] Bump to v23.0.1-SNAPSHOT after the v23.0.0 release #18866
• Make sure release blocker items are closed, list below.
• Draft the release blog post.
• Send requests to cross-post the blog post (CNCF, PlanetScale).

Pre-Release (~1-3 days before)

• Create Release PR. _{^{(We do this earlier to catch any issues in the tool and let CI run.)}}
  • [release-23.0] Release of v23.0.0 #18856
• Update vitess-operator Golang version.
• Open a Pull Request on the website repository for the blog post.
• Update Cobra Docs.

Release (Mon 3 Nov)

• Merge the Release PR.
  • [release-23.0] Release of v23.0.0 #18856
• Tag the release.
  • https://github.com/vitessio/vitess/releases/tag/v23.0.0
• Java release.
• Create vitess-operator Release PR.
  • [release-2.16] Release of v2.16.0 planetscale/vitess-operator#732
• Update release notes on main.
  • [main] Copy v23.0.0 release notes #18865
• Go back to dev mode on the release branch.
  • [release-23.0] Bump to v23.0.1-SNAPSHOT after the v23.0.0 release #18866
• Merge the blog post Pull Request on the website repository.
• Update the website documentation.
• Make sure the release is benchmarked by arewefastyet.
• Docker Images available on DockerHub.
• Close current GitHub Milestone.
  • https://github.com/vitessio/vitess/milestone/85
• Check that release artifacts were generated.
• Merge the vitess-operator Release PR.
• Tag the vitess-operator release.
• Go back to dev mode on vitess-operator.
• Manual update of vitess-operator test code.

Post-Release (Mon 3 Nov)

• Notify the community on Slack for the new release.
• Twitter announcement.
• Remove bypass branch protection rules, if required.
• Close this Issue.