8000 release-24.1: go.mod: bump Pebble to f81f1ede5930 by RaduBerinde · Pull Request #147011 · cockroachdb/cockroach · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

release-24.1: go.mod: bump Pebble to f81f1ede5930 #147011

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
Merged
merged 1 commit into from
May 20, 2025
Merged

release-24.1: go.mod: bump Pebble to f81f1ede5930 #147011

merged 1 commit into from
May 20, 2025

Conversation

RaduBerinde
Copy link
Member

Changes:

  • f81f1ede db: don't require quotes around level number in options section
  • 0fe96563 db: bump maximum {Range,Point}DeletionsBytesEstimate

Release note: none.
Epic: none.

@RaduBerinde
go.mod: bump Pebble to f81f1ede5930
0664f6b 
Changes:

 * [`f81f1ede`](cockroachdb/pebble@f81f1ede) db: don't require quotes around level number in options section
 * [`0fe96563`](cockroachdb/pebble@0fe96563) db: bump maximum {Range,Point}DeletionsBytesEstimate

Release note: none.
Epic: none.
@RaduBerinde RaduBerinde requested review from jbowens and a team May 20, 2025 15:10
@RaduBerinde RaduBerinde requested a review from a team as a code owner May 20, 2025 15:10
@blathers-crl blathers[crl]
Copy link
blathers-crl bot commented May 20, 2025

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Backports should only be created for serious
    issues     or test-only changes.
  • Backports should not break backwards-compatibility.
  • Backports should change as little code as possible.
  • Backports should not change on-disk formats or node communication protocols.
  • Backports should not add new functionality (except as defined
    here).
  • Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
  • All backports must be reviewed by the owning areas TL. For more information as to how that review should be conducted, please consult the backport
    policy    .
If your backport adds new functionality, please ensure that the following additional criteria are satisfied:
  • 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. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
  • Your backport must be accompanied by a post to the appropriate Slack
    channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

@blathers-crl blathers-crl bot added the backport Label PR's that are backports to older release branches label May 20, 2025
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@RaduBerinde RaduBerinde merged commit 4846eb4 into cockroachdb:release-24.1 May 20, 2025
14 of 15 checks passed
@RaduBerinde
Copy link
Member Author

TFTR!

@RaduBerinde RaduBerinde deleted the radu/pebble-release-24.1-f81f1ede5930 branch May 20, 2025 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jbowens jbowens jbowens approved these changes

Assignees
No one assigned
Labels
backport Label PR's that are backports to older release branches target-release-24.1.20
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@RaduBerinde @cockroach-teamcity @jbowens
0