Release of `v22.0.5`

[mattlord]

Note

This release is scheduled for Wed 4 Feb 2026.
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.
  • [release-22.0] Fix some linting issues (#19246) #19247
  • [release-22.0] Fix DROP CONSTRAINT to work the same way as MySQL (#19183) #19240
  • vtorc: improvements to analysis ordering, handle semi-sync disable #19488
  • vtgate: Reject unqualified * after comma in SELECT list #19475
  • [release-22.0] vtorc: support analysis ordering, improve semi-sync rollout (#19427) #19471
• Make sure release blocker items are closed, list below.

Code Freeze (~1-3 days before)

• Code Freeze.
• Create new GitHub Milestone.

Pre-Release (~1-3 days before)

• Create Release PR. _{^{(We do this earlier to catch any issues in the tool and let CI run.)}}
• Update Cobra Docs.

Release (Wed 4 Feb)

• Merge the Release PR.
• Tag the release.
• Update release notes on main.
• Go back to dev mode on the release branch.
• Update the website documentation.
• Make sure the release is benchmarked by arewefastyet.
• Docker Images available on DockerHub.
• Close current GitHub Milestone.
• Check that release artifacts were generated.

Post-Release (Wed 4 Feb)

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