Skip to content

[release-23.0] Code Freeze for v23.0.6 - #20992

Merged
mattlord merged 1 commit into
release-23.0from
release-23.0-code-freeze-1
Sep 3, 2026
Merged

[release-23.0] Code Freeze for v23.0.6#20992
mattlord merged 1 commit into
release-23.0from
release-23.0-code-freeze-1

Conversation

@mattlord

@mattlord mattlord commented Sep 3, 2026

Copy link
Copy Markdown
Member

This Pull Request freezes the branch release-23.0 for v23.0.6

This Pull Request is part of #20935

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

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

Signed-off-by: Matt Lord <mattalord@gmail.com>
Copilot AI balanced review requested due to automatic review settings September 3, 2026 13:39
@mattlord mattlord added Component: General Changes throughout the code base Type: Release labels Sep 3, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 3, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-03T13:41:09.851860Z 739d413 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@vitess-bot vitess-bot Bot added NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work 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 Sep 3, 2026
@mattlord
mattlord merged commit 862d317 into release-23.0 Sep 3, 2026
115 of 117 checks passed
@github-actions github-actions Bot added this to the v23.0.6 milestone Sep 3, 2026
@mattlord
mattlord deleted the release-23.0-code-freeze-1 branch September 3, 2026 13:40
@mattlord mattlord mentioned this pull request Sep 3, 2026
36 tasks
@vitess-bot

vitess-bot Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

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.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The focused workflow change correctly activates the planned release code freeze.

Pull request overview

Enables the release-23.0 code freeze for the v23.0.6 release.

Changes:

  • Makes the code-freeze workflow fail intentionally.
File summaries
File Description
.github/workflows/code_freeze.yml Activates code freeze by exiting with failure.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Balanced

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

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

Labels

Component: Build/CI Component: General Changes throughout the code base 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 Type: Release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants