-
Notifications
You must be signed in to change notification settings - Fork 837
Fusaka/Osaka Releases - v10.1.0 #4150
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
Conversation
Codecov Report✅ All 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:
|
b05c005 to
a1a6429
Compare
|
Sorry, wrong label, not ready yet, release notes missing! |
ed3d48a to
6a10fb9
Compare
|
Hi everyone, we have switched over to the plan to directly do final releases, since timelines aligned better with some work we still wanted to do and the finalization decisions around Fusaka. We still have some minor BPO rework work open, we would then target next Thursday, Nov 6 as release date. |
…eate CHANGELOG headers (AI)
6a10fb9 to
4b56ca8
Compare
|
Will take this in, so that we can do releases in time. |
Follow-up on #4028
Update: some plan adjustments (now directly final releases) + new date, see #4150 (comment)
First release round after restructuring/community-based team.
This is a release round containing all relevant Fusaka/Osaka EIP implementations, see #4132 for an overview. Most implementations should be stable, release round is taking place short after the Sepolia HF taking place. Fusaka support is still labeled as
experimentalout of some care and eventual last-minute changes. It should be relatively safe to integrate already though, state and blockchain interop tests are passing (seevm-osaka-*CI runs on PRs).First AI supported release round with these prompts. Review accordingly.
Releases planned for: Tuesday, October 21 2025
Releases for all active packages (12)