-
Notifications
You must be signed in to change notification settings - Fork 541
Enable announcement banner regarding Fusaka upgrade #1278
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…to be a general-purpose upgrades page
| --- | ||
|
|
||
| ## Fusaka upgrade guide | ||
| Linea will be upgrading to Fusaka (Ethereum's latest EVM upgrade) on December 3-4, 2025 to maintain alignment with Ethereum mainnet. |
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.
Bug: Date inconsistency between announcement and documentation
The Fusaka upgrade date is inconsistent across the documentation. The migration guide states "December 3-4, 2025" while the announcement bar only mentions "December 3, 2025". This discrepancy could confuse node operators about whether the upgrade spans two days or occurs on a single day, potentially causing them to miss the upgrade window or prepare incorrectly.
Additional Locations (1)
| id: "announcement_bar_2025_12_fusaka", | ||
| content: | ||
| '📣 <strong>Running a Linea node?</strong> Linea Beta v4 implements the Pectra upgrade, and, with it, a breaking change for your execution layer node client. You will also need to start running the consensus layer client, Maru, alongside it. Read more <a href="/get-started/how-to/run-a-node/beta-v4-migration">here</a>', | ||
| '📣 <strong>Running a Linea node?</strong> The Fusaka upgrade is coming to Linea Mainnet on December 3, 2025. Learn how to upgrade <a href="/get-started/how-to/run-a-node/beta-v4-migration/#fusaka-upgrade-guide">here</a>', |
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.
Bug: Date inconsistency between announcement and documentation
The announcement bar states the Fusaka upgrade is coming on December 3, 2025, while the documentation specifies December 3-4, 2025. This date mismatch creates confusion about when node operators need to complete their upgrades, potentially causing some to miss the deadline if the upgrade spans two days.
Additional Locations (1)
…igration guide - Remove invalid markdown.hooks configuration from docusaurus.config.js - Add beta-v4-migration page to sidebar navigation under 'Run a node' - Update beta-v4-migration.mdx with latest changes - Fixes missing sidebar menu on Fusaka upgrade guide page
| id: "announcement_bar_2025_12_fusaka", | ||
| content: | ||
| '📣 <strong>Running a Linea node?</strong> Linea Beta v4 implements the Pectra upgrade, and, with it, a breaking change for your execution layer node client. You will also need to start running the consensus layer client, Maru, alongside it. Read more <a href="/get-started/how-to/run-a-node/beta-v4-migration">here</a>', | ||
| '📣 <strong>Running a Linea node?</strong> The Fusaka upgrade is coming to Linea Mainnet on December 3, 2025. Learn how to upgrade <a href="/get-started/how-to/run-a-node/beta-v4-migration/#fusaka-upgrade-guide">here</a>', |
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.
Bug: Date mismatch between announcement and documentation
The announcement bar states the Fusaka upgrade is coming on December 3, 2025, but the documentation page specifies December 3-4, 2025. This inconsistency creates confusion about the actual upgrade date, potentially causing node operators to miss the upgrade window or prepare incorrectly.
Additional Locations (1)
| This upgrade requires updating BOTH your Execution Layer (EL) and Consensus Layer (Maru) clients: | ||
| - Besu: consensys/linea-besu-package:[VERSION_TBD] | ||
| - Maru: consensys/maru:[VERSION_TBD] | ||
| - Geth: 1.16.5 VERSION_TBD |
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.
Bug: Malformed Geth version specification
The Geth version line contains both a specific version number 1.16.5 and a placeholder VERSION_TBD, resulting in Geth: 1.16.5 VERSION_TBD. This appears to be incomplete editing where either the version should be finalized or the placeholder should remain alone, not both together.
Not ready for merge yet -- we need to get more details re: version, and ensure the announcement links to something helpful.
cc @allywhiting
Note
Adds a Fusaka upgrade guide, surfaces it in release notes and sidebar, and enables an announcement banner linking to the guide.
docs/get-started/how-to/run-a-node/beta-v4-migration.mdxwith upgrade steps (EL/CL versions, forkId verification, network flags, Ethstats), and retitles the page to “Upgrade guides”.get-started/how-to/run-a-node/beta-v4-migrationunder “Run a node”.announcement_bar_2025_12_fusakawith link to the Fusaka guide.Written by Cursor Bugbot for commit 47f422d. This will update automatically on new commits. Configure here.