Skip to content

[release-23.0] Bump to v23.0.0-SNAPSHOT after the v23.0.0-RC1 release #18761

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

[release-23.0] Bump to v23.0.0-SNAPSHOT after the v23.0.0-RC1 release #18761

wants to merge 1 commit into from
+6 −6

Conversation

@systay
Copy link
Collaborator

@systay systay commented Oct 16, 2025

Includes the changes required to go back into dev mode (v23.0.0-SNAPSHOT) after the release of v23.0.0-RC1.

This Pull Request is part of #18594

@systay
Back to dev mode: [release-23.0] Bump to v23.0.0-SNAPSHOT after the…
fa2a9bc 
… `v23.0.0-RC1` release

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

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

Signed-off-by: Andres Taylor <[email protected]>
@systay systay added Component: General Changes throughout the code base Type: Release labels Oct 16, 2025
@vitess-bot
Copy link
Contributor

vitess-bot bot commented Oct 16, 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 16, 2025
@systay systay mentioned this pull request Oct 16, 2025
Closed
52 tasks
@github-actions github-actions bot added this to the v23.0.0 milestone Oct 16, 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 16, 2025
@systay systay mentioned this pull request Oct 27, 2025
Closed
40 tasks
@systay
Copy link
Collaborator Author

systay commented Oct 30, 2025

Replaced by #18842

@systay systay closed this Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@frouioui frouioui frouioui approved these changes

@dbussink dbussink Awaiting requested review from dbussink dbussink is a code owner

@harshit-gangal harshit-gangal Awaiting requested review from harshit-gangal harshit-gangal is a code owner

Assignees

No one assigned

Labels

Component: General Changes throughout the code base Type: Release

Projects

None yet

Milestone

v23.0.0

Development

Successfully merging this pull request may close these issues.

3 participants

@systay @frouioui