remove hashicorp-forge/bbolt and replace with official beta release #28916
+19
−75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This removes our dependence on
hashicorp-forge/bbolt
and replaces it with the officialetcd-io/bbolt
. Note that the fix in question, which we created thehashicorp-forge/bbolt
for in the beginning, will be part of the 1.4.0 release, not part of the 1.3.x release that we currently use. That fix is here if people are interested.v1.4.0-beta.0
is the latest tag currently available.I'm guessing we want to move off the beta tag once a stable tag has been cut but given the pace at which this is happening, that might not be for awhile, and the move off of hashicorp-forge/bbolt needs to happen in the next few weeks for compliance reasons.
TODO only if you're a HashiCorp employee
backport/
label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x
, but older release branches will bebackport/ent/x.x.x+ent
.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.