Skip to content

Commit 04d9abb

Browse files
committed
First general release and versioning scheme update notes (Blockchain package)
1 parent 81dc6d2 commit 04d9abb

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

packages/blockchain/CHANGELOG.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,20 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
66
(modification: no type change headlines) and this project adheres to
77
[Semantic Versioning](http://semver.org/spec/v2.0.0.html).
88

9+
## 10.0.0-rc.1 - [ UNPUBLISHED ]
10+
11+
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.
12+
13+
### New Versioning Scheme
14+
15+
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.
16+
17+
As a start we bump all major release versions to version 10, these `RC` releases are the first to be released with the new versioning scheme.
18+
19+
### Other Changes
20+
21+
- Integration of `debug` logging functionality for easier internal debugging, PR [#3676](https://github.com/ethereumjs/ethereumjs-monorepo/pull/3676)
22+
923
## 8.0.0-alpha.1 - 2024-10-17
1024

1125
This is a first round of `alpha` releases for our upcoming breaking release round with a focus on bundle size (tree shaking) and security (dependencies down + no WASM (by default)). Note that `alpha` releases are not meant to be fully API-stable yet and are for early testing only. This release series will be then followed by a `beta` release round where APIs are expected to be mostly stable. Final releases can then be expected for late October/early November 2024.

0 commit comments

Comments
 (0)