Skip to content

Conversation

@mapachurro
Copy link
Collaborator

@mapachurro mapachurro commented Nov 25, 2025

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:
    • Fusaka upgrade guide: Expands docs/get-started/how-to/run-a-node/beta-v4-migration.mdx with upgrade steps (EL/CL versions, forkId verification, network flags, Ethstats), and retitles the page to “Upgrade guides”.
    • Release notes: Adds a brief Fusaka section.
    • Sidebar: Adds link to get-started/how-to/run-a-node/beta-v4-migration under “Run a node”.
  • Site config:
    • Announcement banner: Enables banner announcement_bar_2025_12_fusaka with link to the Fusaka guide.

Written by Cursor Bugbot for commit 47f422d. This will update automatically on new commits. Configure here.

@vercel
Copy link

vercel bot commented Nov 25, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
doc-linea Ready Ready Preview Comment Nov 27, 2025 4:42pm

---

## 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.
Copy link

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)

Fix in Cursor Fix in Web

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>',
Copy link

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)

Fix in Cursor Fix in Web

…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>',
Copy link

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)

Fix in Cursor Fix in Web

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
Copy link

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.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants