You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But at the same time, it's also bumping revm-primitives from 9.0.2 to 10.0.0. Since revm-interpreter does not just use revm-primitives internally, but also as part of its public API, this is a SemVer violation and breaks downstream libraries and applications.
Since revm-interpreter is also used by say revm, these other crates are also broken as a result.
For a library that depends on say revm-interpreter v10.0.1, it might also import revm-primitives 9 to use with the interpreter. Now when it's imported by apps/libs further downstream they wouldn't use the library's lock file (if any) but instead resolve to the latest version on crates.io, which means a revm-interpreter version that excepts revm-primitives 10, and now the library's code stops working.
I remember this happened a while ago as well, so I decided to post it here to raise awareness.
The text was updated successfully, but these errors were encountered:
revm-interpreter
bumped its version from10.0.2
to10.0.3
here: 4f09399#diff-39002a8f7750a6f47016f15b058b99efb706c660821f76fbb8a7740c9814b45aBut at the same time, it's also bumping
revm-primitives
from9.0.2
to10.0.0
. Sincerevm-interpreter
does not just userevm-primitives
internally, but also as part of its public API, this is a SemVer violation and breaks downstream libraries and applications.Since
revm-interpreter
is also used by sayrevm
, these other crates are also broken as a result.For a library that depends on say
revm-interpreter
v10.0.1, it might also importrevm-primitives
9 to use with the interpreter. Now when it's imported by apps/libs further downstream they wouldn't use the library's lock file (if any) but instead resolve to the latest version on crates.io, which means arevm-interpreter
version that exceptsrevm-primitives
10, and now the library's code stops working.I remember this happened a while ago as well, so I decided to post it here to raise awareness.
The text was updated successfully, but these errors were encountered: