chore: bump badger dep from v3 to v4 #292
Open
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.
🔧 Changes
In this PR we are bumping
github.com/dgraph-io/badger
from v3.2103.2 to v4.2.0 (Changelog).Furthermore the Go version within the
go.mod
file was also updated from 1.17 to 1.22 (latest). As far as I can tell Badger v4 doesn't rely on features or standard library changes introduced after Go 1.17. This was done mainly to avoid running commands such asgo mod tidy -go=1.16 && go mod tidy -go=1.17
for dependency bumps in the future.🔬 Testing
Other than running
go test -race ./...
I executed the following as well:go run main.go kv set myKey myValue go run main.go kv get myKey go run main.go kv list go run main.go kv reset go run main.go kv sync go run main.go kv delete myKey
No issues found.
I also ran
govulncheck ./...
with the following result:Note
I'm more than happy to help out with bumping any other deps if there's an appetite, I was mostly interested in having the latest version of badger.