chore: pin reth dependencies to a release #964
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
Building against a moving target is hard. It's just good practice to have everyone working against a consistent version of the dependency anyway. The "version" attribute was basically ignored by cargo. So those are the theoretical reasons. Here is a practical one: Basic things are changing about the RPC structs, like the type of the transaction hashes, even in just the last few weeks.
njgheorghita
approved these changes
Oct 6, 2023
|
Yeah, I suppose one mechanism is we'll be forced to update as we push features upstream. (which we will likely end up doing for the state network) But I agree that it would be nice to have more. I opened #969 to track |
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.
Building against a moving target is hard. It's just good practice to have everyone working against a consistent version of the dependency anyway. The "version" attribute was basically ignored by cargo.
So those are the theoretical reasons. Here is a practical one: Basic things are changing about the RPC structs, like the type of the transaction hashes, even in just the last few weeks.
Split from #963