-
Notifications
You must be signed in to change notification settings - Fork 834
v10 Breaking Releases #4028
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
v10 Breaking Releases #4028
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
467bb84
to
b3e4f89
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment at the changelog, LGTM in general 😄 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, great work! Ship it 🎉 😄 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks fine. If my one comment is too nitpicky, feel free to merge without it
|
||
### Overview | ||
|
||
This release is part of the `v10` breaking release round making the `EthereumJS` libraries compatible with the [Pectra](https://eips.ethereum.org/EIPS/eip-7600) hardfork going live on Ethereum `mainnet` on May 7 2025. Beside the hardfork update these releases mark a milestone in our release history since they - for the first time ever - bring the full `Ethereum` protocol stack - including the `EVM` - to the browser without any restrictions anymore, coming along with other substantial updates regarding library security and functionality. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I get anxious about this phrasing "full stack to the browser" language. Devp2p explicitly does not work in the browser. Can we at something like "the full set of Ethereum primitives"?
Disregard if I'm being too pedantic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TBH I think really no one will think about devp2p when reading this sentence, I think this is just our own over-knowledged inside view. 🙂 😋
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚀 🚀
Just published the following releases on npm:
|
v10 breaking release round for the monorepo, making the libraries Pectra-ready and coming with a strong set of refactorings and improvements, namely making everything more tree-shakeable, reduce bundle sizes, bringing a full pure-JS library stack, substantially reduce dependencies, among others.
Follow-up on
rc.1
releases #3886 (see #3936 for release note addition)Main release notes along
alpha.1
releases #3722Releases targeted for Tuesday, April 29 2025