docs: release v5.1.0 for Alpha V5 and Testnet - #25085
Merged
Merged
Conversation
AztecBot
added
A-documentation
AztecBot
changed the title
alejoamiras
marked this pull request as ready for review
August 3, 2026 18:23
alejoamiras
self-requested a review
August 3, 2026 18:23
alejoamiras
approved these changes
Aug 3, 2026
## Summary - publish `v5.1.0` as the shared release for both **Alpha V5** and **Testnet** across developer and network/operator documentation - configure both `mainnet` and `testnet` selectors to resolve to the same `v5.1.0` snapshot, rendering `Alpha / Testnet (v5.1.0)` - remove the deprecated `v5.0.1` developer and network snapshots - regenerate the v5.1.0 Aztec, wallet, operator, Node JSON-RPC, Aztec.nr, and TypeScript API references - provide identical generated API artifacts under the stable `mainnet` and `testnet` paths, with the shared snapshot using the canonical `mainnet` paths - refresh Testnet network metadata from `https://v5.testnet.rpc.aztec-labs.com` and checksum the documented Sepolia addresses - carry forward release-valid documentation fixes and role-based operator structure while resolving code snippets against the `v5.1.0` tag ## Release details The Testnet RPC still reports node version `5.0.0`, so this uses the requested pre-release workflow for the tagged `v5.1.0` upgrade. The RPC-confirmed Testnet L1 deployment, chain ID (`11155111`), and rollup version (`1821665230`) remain unchanged. Alpha V5 retains its existing deployment metadata while its documentation version advances to the same `v5.1.0` release. Canonical Testnet L2 values are derived from the `v5.1.0` tooling where the pre-upgrade RPC differs: - MultiCall Entrypoint: `0x246d60af8b79a5dceece7d2388921203401c0df02ce674c5781c6c2162922986` - Sponsored FPC: `0x130925fbd734a252e3d8ddff87f6c346052dd5c13314eb96026b32baa1923296` The Sponsored FPC address changed from the previous docs and must be funded for Testnet use. Alpha V5 continues to document Sponsored FPC as not deployed. ## Validation - `MAINNET_TAG=5.1.0 TESTNET_TAG=5.1.0 RELEASE_TYPE=mainnet COMMIT_TAG=v5.1.0 yarn build` - CSpell: 0 issues - redirect targets: valid - Docusaurus production build: successful - developer and operator pages render `Alpha / Testnet (v5.1.0)` - `yarn validate:api-ref-links` - 112 API links checked - 0 broken links - 0 version mismatches - generated `mainnet` and `testnet` Aztec.nr and TypeScript API directories are byte-identical - new versioned snapshots contain no unresolved release/include macros - version configs and version lists contain one shared `v5.1.0` snapshot for both Alpha V5 and Testnet The build retains existing non-fatal broken-anchor warnings from generated CLI aliases and operator compose-page anchors. --- *Updated by [claudebox](https://claudebox.work/v2/sessions/8446a113e20bc334/jobs/3) · group: `slackbot` · requested by Alejo Amiras · [Slack thread](https://aztecfoundation.slack.com/archives/C0B24G1GFGB/p1785769938239119?thread_ts=1785769938.239119&cid=C0B24G1GFGB)* --- *Created by [claudebox](https://claudebox.work/v2/sessions/8446a113e20bc334/jobs/2) · group: `slackbot` · requested by Alejo Amiras · [Slack thread](https://aztecfoundation.slack.com/archives/C0B24G1GFGB/p1785769938239119?thread_ts=1785769938.239119&cid=C0B24G1GFGB)*
AztecBot
force-pushed
the
cb/release-docs-v5.1.0
branch
from
August 3, 2026 18:28
f383e54 to
d702dcd
Compare
AztecBot
enabled auto-merge
August 3, 2026 18:28
AztecBot
added this pull request to the merge queue
Aug 3, 2026
rangozd
pushed a commit
to rangozd/aztec-packages
that referenced
this pull request
Aug 5, 2026
## Summary - replace the stale `v5.1.0` network sidebar snapshot with the current role-based operator sidebar from `docs/sidebars-operate.js` - confirm the current and versioned operator docs already contain the same 83-file role-based documentation tree from [aztec-packages#24219](AztecProtocol#24219) - update both release-doc skills so post-tag docs reconciliation includes matching sidebar changes and a semantic consistency check ## Root cause [aztec-packages#25085](AztecProtocol#25085) generated the sidebar from the pre-backport `v5.1.0` tag, then carried the current operator pages into the released snapshot without updating the versioned sidebar. The build passed because the legacy pages referenced by the stale sidebar still existed. ## Validation - `docs/sidebars-operate.js` and `docs/network_versioned_sidebars/version-v5.1.0-sidebars.json` are deeply equal - current and versioned operator docs contain the same 83 paths - `MAINNET_TAG=5.1.0 TESTNET_TAG=5.1.0 RELEASE_TYPE=mainnet COMMIT_TAG=v5.1.0 yarn build` - CSpell: 0 issues - redirects: valid - 112 API links checked - 0 broken links - 0 version mismatches - both `/operate/operators` and `/operate/alpha/operators` render Guided setup, Full node, Solo sequencer, Staking provider, and Operator tooling The build retains the existing non-fatal generated CLI and compose-page anchor warnings. --- *Created by [claudebox](https://claudebox.work/v2/sessions/8446a113e20bc334/jobs/6) · group: `slackbot` · requested by Alejo Amiras · [Slack thread](https://aztecfoundation.slack.com/archives/C0B24G1GFGB/p1785769938239119?thread_ts=1785769938.239119&cid=C0B24G1GFGB)*
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v5.1.0as the shared release for both Alpha V5 and Testnet across developer and network/operator documentationmainnetandtestnetselectors to resolve to the samev5.1.0snapshot, renderingAlpha / Testnet (v5.1.0)v5.0.1developer and network snapshotsmainnetandtestnetpaths, with the shared snapshot using the canonicalmainnetpathshttps://v5.testnet.rpc.aztec-labs.comand checksum the documented Sepolia addressesv5.1.0tagRelease details
The Testnet RPC still reports node version
5.0.0, so this uses the requested pre-release workflow for the taggedv5.1.0upgrade. The RPC-confirmed Testnet L1 deployment, chain ID (11155111), and rollup version (1821665230) remain unchanged. Alpha V5 retains its existing deployment metadata while its documentation version advances to the samev5.1.0release.Canonical Testnet L2 values are derived from the
v5.1.0tooling where the pre-upgrade RPC differs:0x246d60af8b79a5dceece7d2388921203401c0df02ce674c5781c6c21629229860x130925fbd734a252e3d8ddff87f6c346052dd5c13314eb96026b32baa1923296The Sponsored FPC address changed from the previous docs and must be funded for Testnet use. Alpha V5 continues to document Sponsored FPC as not deployed.
Validation
MAINNET_TAG=5.1.0 TESTNET_TAG=5.1.0 RELEASE_TYPE=mainnet COMMIT_TAG=v5.1.0 yarn buildAlpha / Testnet (v5.1.0)yarn validate:api-ref-linksmainnetandtestnetAztec.nr and TypeScript API directories are byte-identicalv5.1.0snapshot for both Alpha V5 and TestnetThe build retains existing non-fatal broken-anchor warnings from generated CLI aliases and operator compose-page anchors.
Updated by claudebox · group:
slackbot· requested by Alejo Amiras · Slack threadCreated by claudebox · group:
slackbot· requested by Alejo Amiras · Slack thread