Some last round RC Release Note Updates #3936
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:
|
| ## 10.0.0-dev-rc.1 - 2025-03-24 | ||
|
|
||
| This is the first (and likely the last) round of `RC` releases for the upcoming breaking releases, following the `alpha` releases from October 2024. The releases are somewhat delayed (sorry for that), but final releases can now be expected very very soon, to be released once the Ethereum [Pectra](https://eips.ethereum.org/EIPS/eip-7600) hardfork is scheduled for mainnet and all EIPs are fully finalized. Pectra will then also be the default hardfork setting for all EthereumJS libraries. | ||
| This is the first (and likely the last) round of `RC` releases for the upcoming breaking releases, following the `alpha` releases from October 2024 (see `alpha` release release notes for full/main change description). The releases are somewhat delayed (sorry for that), but final releases can now be expected very very soon, to be released once the Ethereum [Pectra](https://eips.ethereum.org/EIPS/eip-7600) hardfork is scheduled for mainnet and all EIPs are fully finalized. Pectra will then also be the default hardfork setting for all EthereumJS libraries. |
There was a problem hiding this comment.
Can we maybe link this to a sector in the README?
Note: binarytree has no alpha release, see: https://github.com/ethereumjs/ethereumjs-monorepo/blob/53c9f32c6026d05d5ff51f218578eaa1aa720923/packages/binarytree/CHANGELOG.md#1000-dev-rc1---2025-03-24
For the block release you could link for instance to: https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/block/CHANGELOG.md#600-alpha1---2024-10-17 (note: this is not a permalink so if we do update the file but not the header titles in the file itself, it should link to the correct part of the changelog even if we update it!)
| ### New Versioning Scheme | ||
|
|
||
| This breaking release round will come with a new versioning scheme (thanks to @paulmillr for the [suggestion](https://github.com/ethereumjs/ethereumjs-monorepo/issues/3748)), aligning the package numbers on breaking releases for all EthereumJS packages. This will make it easier to report bugs ("bug happened on EthereumJS version 10 releases"), reason about release series and make library compatibility more transparent and easier to grasp. | ||
| This breaking release round will come with a new versioning scheme (thanks to paulmillr for the [suggestion](https://github.com/ethereumjs/ethereumjs-monorepo/issues/3748)), aligning the package numbers on breaking releases for all EthereumJS packages. This will make it easier to report bugs ("bug happened on EthereumJS version 10 releases"), reason about release series and make library compatibility more transparent and easier to grasp. |
There was a problem hiding this comment.
Nit: what is the motivation to remove the @? It is now not directly clear it's an username I'd say.
2 participants
Post-release, but does not matter, merge ready.