Skip to content

Mesa preflight: post-hard-fork banner and bump to 4.0.0-preflight-3f038cb#1193

Merged
dkijania merged 2 commits intomainfrom
dkijania/mesa-post-hardfork-3f038cb
Apr 27, 2026
Merged

Mesa preflight: post-hard-fork banner and bump to 4.0.0-preflight-3f038cb#1193
dkijania merged 2 commits intomainfrom
dkijania/mesa-post-hardfork-3f038cb

Conversation

@dkijania
Copy link
Copy Markdown
Member

Summary

  • The Mesa preflight network hard-forked at 2026-04-27 14:00 UTC. The post-fork chain runs 4.0.0-preflight-3f038cb, which raises the transaction protocol version to 5.0.0 — a breaking wire-format change that retires every pre-fork build.
  • Rewrites the warning banners on network-upgrades/index.mdx, mesa/preflight-network.mdx, and mesa/archive-upgrade.mdx to describe the hard fork as completed (rather than upcoming) and to call out the protocol version bump.
  • Promotes 4.0.0-preflight-3f038cb to the current preflight build across every Docker tag, Debian package pin, and inline command. Demotes 4.0.0-preflight-stop-2967b39 (stop-slot) and 4.0.0-preflight1-b649c79 (original) to a historical-only list with an explicit incompatibility note.
  • Regenerates static/llms-full.txt to keep the check-llms-txt CI check green.

This PR simulates a real hard-fork rollout for the preflight network so the docs reflect the post-fork operator path end-to-end.

Test plan

  • CI: validate-docker-images passes (the new 4.0.0-preflight-3f038cb tags must be reachable on the registry, otherwise the validator will need an angle-bracket placeholder pass).
  • CI: check-llms-txt passes against the regenerated static/llms-full.txt.
  • CI: Vercel preview builds and renders the three updated pages without MDX errors.
  • Manual: open the Vercel preview and confirm the post-fork banner renders on /network-upgrades, /network-upgrades/mesa/preflight-network, and /network-upgrades/mesa/archive-upgrade, and that the build matrix on the preflight page reads correctly.

🤖 Generated with Claude Code

The Mesa preflight network hard-forked at 2026-04-27 14:00 UTC. The
post-fork chain runs the Mesa release 4.0.0-preflight-3f038cb, which
raises the transaction protocol version to 5.0.0 — a breaking
wire-format change that retires every pre-fork build, including the
stop-slot release 4.0.0-preflight-stop-2967b39.

Update the network-upgrades index, preflight-network, and archive-upgrade
pages to reflect the post-fork state: warning banners now describe the
hard fork as completed rather than upcoming, the preflight build matrix
is rewritten around 4.0.0-preflight-3f038cb (with prior builds demoted
to a historical list), and every Docker tag, Debian package pin, and
inline command is bumped accordingly. Also regenerate static/llms-full.txt.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 27, 2026

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

Project Deployment Actions Updated (UTC)
docs2 Ready Ready Preview, Comment Apr 27, 2026 2:07pm

Request Review

…bility

The Mesa preflight hard fork occurred at 13:00 UTC, not 14:00 UTC.
Correct every timestamp on the network-upgrades index, preflight-network,
and archive-upgrade pages.

Also document the matching SDK release: zkApp developers must use
o1js@3.0.0-mesa.698ca, the first o1js version that targets transaction
protocol v5.0.0. Earlier o1js releases produce transactions that the
post-fork chain will reject. Add this guidance to the post-fork banners
on the index and preflight-network pages, and list o1js@3.0.0-mesa.698ca
alongside the daemon build matrix on preflight-network.

Regenerate static/llms-full.txt to match.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@SanabriaRusso
Copy link
Copy Markdown
Member

Rosetta recently succeeded, then approving,.

@SanabriaRusso SanabriaRusso self-requested a review April 27, 2026 16:38
@dkijania dkijania merged commit 5657afe into main Apr 27, 2026
4 of 6 checks passed
@dkijania dkijania deleted the dkijania/mesa-post-hardfork-3f038cb branch April 27, 2026 16:52
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.

2 participants