Repository navigation
docs: adapt the docs tooling to aztec-node's main and v6 branches - #25734
Merged
Merged
Conversation
Without COMMIT_TAG (previews, local builds) the legacy macros resolved to next and latest. aztec-node has no next ref, so 38 source links and the aztec-nr Nargo tags pointed nowhere. They now take the ref docs/aztec-node.json pins. Release cuts set COMMIT_TAG and are unchanged. Three @aztec-foundation installs used the Labs macro and named the Labs version in every build; they now use #include_foundation_version_without_prefix.
From 2026-11-04 aztec-node carries v7 on main and v6 on a v6 branch, with hand backports. The dev pin moves to the newest nightly of main's major and is checked to be on main; release cuts pin their tag. The release skills now find hand backports in migration-note triage (TBD and Unreleased) and expect adapted backports on both sides of the content check. update-doc-references reports, without editing, v6 PRs the pin lacks; updating-changelog takes a PR's major from its base. networks.md and support.md no longer name a development branch or aztec-node's nonexistent next.
…rry a v7 line A v6.x release is cut from the dev docs' pages and examples, so it works only while they are v6 content. The pin check now tests that the recorded commit is on v6, and update-doc-references gates PRs into main (v7) instead of PRs into v6.
alejoamiras
marked this pull request as ready for review
November 5, 2026 14:57
asterite
approved these changes
Nov 5, 2026
alejoamiras
added a commit
that referenced
this pull request
Nov 5, 2026
The docs tooling learns about dev lines: a copy of the dev docs under `docs/lines/<line>/` that follows one aztec-node branch with its own pin. This PR adds no line, so the site, CI and Netlify behave as before. The next PR adds the v6 line. Stacked on #25734. - Adds a fingerprint of what a production build serves, so every PR can show that production is unchanged. - The aztec-node pin tool fetches, pins and provisions a line on its own, with its own contracts package, and refuses a tag from another major. - Pages in a line take their code snippets, versions and links from that line. - A page that quotes the other line's examples or contracts fails the build. - A line's examples build outside the repository, and its references are checked against its own code. Main's examples build as before. Tests: - New unit tests cover each of these. - The script tests pass without installed packages. - The production fingerprint is identical before and after. - The line tooling passes against a temporary v6 copy.
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
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
aztec-node now carries v7 on
mainand v6 on a newv6branch, with backports made by hand. Until the docs can carry both lines, the dev docs stay on v6 nightlies, because a v6.x release is cut from them. This PR updates the docs tooling text and the four docs skills for that layout. It also fixes the version macros, which pointed at an aztec-node ref that does not exist.The pin script needs no change, since its tag pattern accepts v7 tags. The pin itself does not move here.
Before merge
main's first nightly isv7.0.0-nightly.20261105, which matches the example on the networks page.v7.0.0-nightly.20261105on a copy of the pin passed. The committed pin is untouched.next, and the docs checks pass on it.Changes
v6.nextandlatest. This fixes 38 dead aztec-node links and the aztec-nr tags in previews and local builds. Release cuts are unchanged.main(v7) whose merge commit is not in the pin is analyzed and reported, and gets no source edits.mainand7.0.0-nightly.<date>.Not in this PR
v6leftmain, so the pin check holds either way. The networks page doesn't mention v6 nightlies.Test plan
node_modules: 45 pass, 1 skip../bootstrap.sh check: the skills lint, the reference check, and the netlify and warnings checks all pass.v7.0.0-nightly.20261105on a copy of the pin: fetched, all four noir archives attested, and the toolchain unchanged (bb 6.0.0-rc.7, noir 1.0.0-rc.3).behindfor the current pin.