Skip to content

Conversation

@systay
Copy link
Collaborator

@systay systay commented Oct 29, 2025

Includes the release notes and release commit for the v23.0.0-RC2 release. Once this PR is merged, we will be able to tag v23.0.0-RC2 on the merge commit.

This Pull Request is part of #18822

This commit was made automatically by the vitess-releaser tool.

See https://github.com/vitessio/vitess-releaser

Signed-off-by: Andres Taylor <[email protected]>
This commit was made automatically by the vitess-releaser tool.

See https://github.com/vitessio/vitess-releaser

Signed-off-by: Andres Taylor <[email protected]>
@vitess-bot
Copy link
Contributor

vitess-bot bot commented Oct 29, 2025

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot added NeedsBackportReason If backport labels have been applied to a PR, a justification is required NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Oct 29, 2025
@systay systay mentioned this pull request Oct 29, 2025
40 tasks
@github-actions github-actions bot added this to the v23.0.0 milestone Oct 29, 2025
@systay systay removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says NeedsIssue A linked issue is missing for this Pull Request NeedsBackportReason If backport labels have been applied to a PR, a justification is required labels Oct 29, 2025
@systay systay merged commit 2c76877 into release-23.0 Oct 29, 2025
101 of 117 checks passed
@systay systay deleted the release-23.0-create-release-3 branch October 29, 2025 14:33
@codecov
Copy link

codecov bot commented Oct 29, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.70%. Comparing base (58344e1) to head (7ccf77d).
⚠️ Report is 13 commits behind head on release-23.0.

Additional details and impacted files
@@              Coverage Diff              @@
##           release-23.0   #18840   +/-   ##
=============================================
  Coverage         69.70%   69.70%           
=============================================
  Files              1605     1606    +1     
  Lines            214449   214482   +33     
=============================================
+ Hits             149475   149506   +31     
- Misses            64974    64976    +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Component: General Changes throughout the code base Type: Release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants