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.

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

release-23.1: tree: fix statement tag for tree.ShowSequences #106797

Merged
merged 1 commit into from Jul 14, 2023

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Jul 14, 2023

Backport 1/1 commits from #106790 on behalf of @andyyang890.

/cc @cockroachdb/release


Epic: None

Release note (bug fix): The statement tag for SHOW SEQUENCES is now
corrected to be SHOW SEQUENCES instead of SHOW SCHEMAS.


Release justification: Bug fix

Release note (bug fix): The statement tag for `SHOW SEQUENCES` is now
corrected to be `SHOW SEQUENCES` instead of `SHOW SCHEMAS`.
@blathers-crl blathers-crl bot requested a review from a team as a code owner July 14, 2023 00:10
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-106790 branch from b74b7c3 to 0a09322 Compare July 14, 2023 00:10
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Jul 14, 2023
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-106790 branch from 0182e86 to 1305d06 Compare July 14, 2023 00:10
@blathers-crl
Copy link
Author

blathers-crl bot commented Jul 14, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@blathers-crl
Copy link
Author

blathers-crl bot commented Jul 14, 2023

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@andyyang890 andyyang890 merged commit 2463cca into release-23.1 Jul 14, 2023
5 of 6 checks passed
@andyyang890 andyyang890 deleted the blathers/backport-release-23.1-106790 branch July 14, 2023 01:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants