Skip to content
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

[release-21.0] Bump to v21.0.0-SNAPSHOT after the v21.0.0-RC1 release #16955

Merged
merged 1 commit into from
Oct 15, 2024
Merged

[release-21.0] Bump to v21.0.0-SNAPSHOT after the v21.0.0-RC1 release #16955

merged 1 commit into from
Oct 15, 2024

Conversation

vitess-bot
Copy link
Contributor

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

@rohit-nayak-ps
Back to dev mode: [release-21.0] Bump to v21.0.0-SNAPSHOT after the…
80a0fe8 
… `v21.0.0-RC1` release

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

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

Signed-off-by: Rohit Nayak <[email protected]>
@vitess-bot vitess-bot requested a review from deepthi as a code owner October 15, 2024 05:40
@vitess-bot vitess-bot added Component: General Changes throughout the code base Type: Release labels Oct 15, 2024
@vitess-bot vitess-bot
Copy link
Contributor

vitess-bot bot commented Oct 15, 2024

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 15, 2024
@vitess-bot vitess-bot mentioned this pull request Oct 15, 2024
Closed
35 tasks
@frouioui frouioui 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 15, 2024
@github-actions github-actions bot added this to the v21.0.0 milestone Oct 15, 2024
@codecov Codecov
Copy link

codecov bot commented Oct 15, 2024 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.44%. Comparing base (7908b43) to head (80a0fe8).
Report is 1 commits behind head on release-21.0.

Additional details and impacted files 
@@               Coverage Diff                @@
##           release-21.0   #16955      +/-   ##
================================================
- Coverage         69.45%   69.44%   -0.01%     
================================================
  Files              1570     1570              
  Lines            203835   203835              
================================================
- Hits             141564   141562       -2     
- Misses            62271    62273       +2

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

@rohit-nayak-ps rohit-nayak-ps merged commit 3b6632e into release-21.0 Oct 15, 2024
202 of 203 checks passed
@rohit-nayak-ps rohit-nayak-ps deleted the release-21.0-back-to-dev-mode-4 branch October 15, 2024 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rohit-nayak-ps rohit-nayak-ps rohit-nayak-ps approved these changes

@frouioui frouioui frouioui approved these changes

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

@ajm188 ajm188 Awaiting requested review from ajm188 ajm188 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
v21.0.0
Development

Successfully merging this pull request may close these issues.
3 participants
@vitess-bot @frouioui @rohit-nayak-ps