-
Notifications
You must be signed in to change notification settings - Fork 572
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.
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
Revm 16.0.0 depends on alloy 0.3, resulting in duplicate crates #1828
Comments
Releases are done from For why there is major version number bumped is because of the dependency bump on The |
Thanks for the clarification! |
No problem, and thank you for using revm! |
Just wanted a clarification on this, if we were to fork AlloyDB and maintain an updated version ourselves, may we use the crate name |
This seems reasonable. There is a potential future where this is included directly in alloy, but until then be free to publish revm-alloy-db. |
Have published new revm with bumped AlloyDB |
The
alloydb
feature provided by revm 16.0.0 still depends on outdated alloy crates. This results in duplicate (and conflicting) dependencies foralloy-eip7702
.Additionally, I've noticed that the 2 major version change releases today where based on a branch which diverged from main on Sept 9th. The main branch seemingly already has all the up-to-date dependencies. Are there plans to release a version on cargo based on the main branch anytime soonish?
The text was updated successfully, but these errors were encountered: