Repository navigation
Tracking: prepare and manage release_v4.8.3 branch #6957
Description
Activity
Please comment below with any bugs or feature requests you'd like considered for the next release.
- added sub-issues
on Sep 9, 2026 - added sub-issues
on Sep 9, 2026 7 remaining items
- pinned this issue
on Sep 10, 2026 - added a sub-issue
on Sep 17, 2026 For release QA, please include an in-place upgrade test from v4.8.2 using an existing production-like database, followed by restart recovery and continued synchronization. A mixed-version peer test between v4.8.2 and v4.8.3 would also be useful, comparing consensus-critical results such as block and transaction roots, receipts, and account state at fixed heights. This can catch database, serialization, or compatibility regressions that unit and API tests may miss.
- added sub-issues
on Sep 18, 2026 - removed a sub-issue
on Sep 22, 2026
This issue is to coordinate the creation and tracking of the
release_v4.8.3branch fromdevelop.Branch Details
v4.8.3release_v4.8.3developTasks
release_v4.8.3branch fromdeveloprelease_v4.8.3(e.g., version bump, changelog, fixes, features)release_v4.8.3release_v4.8.3back tomasterwhen testing is completeGreatVoyage-v4.8.3(Ockham)onmasterand releasemasterback todevelop(if applicable)Notes
Once the
release_v4.8.3branch is created, it will act as the staging area for all final updates and fixes for this release.Any non-release-related changes should continue in
develop.Release date
The release is targeted for end of November
PRs