Downgrade Level DB to Stable Version #13671
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prestonvanloon
approved these changes
Feb 29, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
nalepae
pushed a commit
that referenced
this pull request
Feb 29, 2024
* downgrade level db * fix current issues * update geth * Fix zstd build. The patch is now longer needed now that bazel-contrib/rules_go#3411 is fixed. * Revert "update geth" This reverts commit 2a7c51a. * change to hex --------- Co-authored-by: Preston Van Loon <pvanloon@offchainlabs.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
Bug Fix
What does this PR do? Why is it needed?
This downgrades our leveldb version to a stable version so that consumers of prysm do not use an unstable version of leveldb.
This PR also updates our geth dependency to the deneb mainnet release.Which issues(s) does this PR fix?
N.A
Other notes for review