docs: add mainnet developer docs version (v4.2.0-aztecnr-rc.2)#22106
Merged
critesjosh merged 1 commit intonextfrom Mar 27, 2026
Merged
docs: add mainnet developer docs version (v4.2.0-aztecnr-rc.2)#22106critesjosh merged 1 commit intonextfrom
critesjosh merged 1 commit intonextfrom
Conversation
critesjosh
changed the title
critesjosh
changed the title
critesjosh
changed the title
sklppy88
approved these changes
Mar 27, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
AztecBot
force-pushed
the
docs/alpha-mainnet-versioning
branch
from
d5e3dfb to
84af660
Compare
## Summary **Developer docs changes:** - Introduces explicit version config (`developer_version_config.json`) that maps release types (mainnet/testnet/devnet/nightly) to version strings, replacing fragile substring matching - Adds mainnet as a first-class release type in API reference pages, doc generation scripts, preprocessing macros, and Docusaurus config - Removes the `ignition` alias from conditional content processing, version macros, and tests - Renames "Ignition" to "Alpha (Mainnet)" in developer-facing docs and networks page - Adds `v4.2.0-aztecnr-rc.2` versioned developer docs with `@latest` pinned to specific version - Adds mainnet API docs (`static/aztec-nr-api/mainnet/`, `static/typescript-api/mainnet/`) - Regenerates CLI reference docs (new `get-fee-juice-balance` command, `--wait-for-status` options) - Updates networks page with mainnet RPC endpoint, L2 contract addresses, and active transaction support **Operator/network docs are NOT included** — network docs remain on the existing ignition-based versioning (`network_versions.json` with substring matching). A separate PR will handle the operator docs version cut. **Supporting changes:** - Updates CLAUDE.md, README.md, release-docs SKILL.md, and nightly workflow to reflect config-based developer versioning - Adds nargo version verification to Netlify preview build to catch stale cache - `update_docs_versions.sh` now only supports the `developer` instance; network docs are managed by editing `network_versions.json` directly ## Test plan - [x] `yarn build` completes successfully - [ ] `yarn start` serves correctly with the new version config - [ ] Version dropdown shows "Alpha (v4.2.0-aztecnr-rc.2)" as default for developer docs - [ ] Operator docs version dropdown still shows Ignition and Testnet - [ ] API reference links resolve correctly for each version - [ ] Conditional content renders correctly for each `RELEASE_TYPE` - [ ] Preprocessor tests pass (`node --test src/preprocess/__tests__/`) 🤖 Generated with [Claude Code](https://claude.com/claude-code)
AztecBot
force-pushed
the
docs/alpha-mainnet-versioning
branch
from
84af660 to
b3f4a7e
Compare
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Collaborator
|
❌ Failed to cherry-pick to |
critesjosh
pushed a commit
that referenced
this pull request
Apr 1, 2026
Backport config-based version management system and network docs migration from Ignition to Alpha. This ensures the v4-next release line has the updated docs infrastructure for straightforward releases. Key changes: - Add developer_version_config.json and network_version_config.json as source of truth for type->version mappings (replaces substring matching) - Update docusaurus.config.js with syncVersionsFromConfig() and mainnet support for both developer and network docs instances - Rewrite update_docs_versions.sh with config-based reconciliation - Update preprocessors to read defaults from config, remove ignition alias - Add RELEASE_TYPE env var support to API doc generation scripts - Add nargo version verification to netlify preview builds - Update nightly docs workflow for config-based version management - Add v4.1.2 Alpha network versioned docs with HA guide and v4.x changelog - Create release-docs skill for Claude Code assisted releases - Update netlify redirects for /operate/ paths
3 tasks
critesjosh
added a commit
that referenced
this pull request
Apr 6, 2026
… (#22223) ## Summary - Backports docs build and release infrastructure changes from #22106 and #22144 to the v4-next staging branch - Includes versioned docs preprocessing, redirect validation, and release workflow updates ## Test plan - [ ] Verify docs build passes - [ ] Confirm redirect validation script works correctly - [ ] Check versioned content preprocessing handles v4 content properly
AztecBot
added a commit
that referenced
this pull request
Apr 8, 2026
BEGIN_COMMIT_OVERRIDE fix: pippenger edge case (#22256) cherry-pick: fix: separate fisherman StatefulSet from rpc-node and stop archiver pollution (#22183) — WITH CONFLICTS fix: separate fisherman StatefulSet from rpc-node and stop archiver pollution (backport #22183) (#22284) fix: preserve DeployAccountMethod type in with() method chaining (#22322) docs: backport docs build/release infrastructure from #22106 and #22144 (#22223) chore(docs): remove v5 nightly and devnet versioned docs (backport #22193) (#22236) chore: improve release-docs skill and add release-network-docs skill (#22328) chore: remove dead to_be_bytes fn (#22243) fix: correct args length in `#[authorize_once]` (#22209) chore: fix inconsistent usage of contract class hash fn (#22248) chore: delete old field comparison fns in favor of lt (#22249) fix: all account overrides + gas limits (#22173) feat: allow for runtime length arrays of sorts and selects (#22250) chore: remove dead pub global vars reexport (#22244) chore: changed default wait behavior (#22325) chore: apply code consistency consolidation (#22251) fix(docs): simplify TypeScript API reference links (backport #22232) (#22369) fix: remove detailed revert codes (#22380) fix: backport #21673 — prevent HA peer proposals from blocking equivocation in duplicate proposal test (#21693) fix: subfield note selectors (#22211) END_COMMIT_OVERRIDE
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
4 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
Developer docs changes:
developer_version_config.json) that maps release types (mainnet/testnet/devnet/nightly) to version strings, replacing fragile substring matchingignitionalias from conditional content processing, version macros, and testsv4.2.0-aztecnr-rc.2versioned developer docs with@latestpinned to specific versionstatic/aztec-nr-api/mainnet/,static/typescript-api/mainnet/)get-fee-juice-balancecommand,--wait-for-statusoptions)Operator/network docs are NOT included — network docs remain on the existing ignition-based versioning (
network_versions.jsonwith substring matching). A separate PR will handle the operator docs version cut.Supporting changes:
update_docs_versions.shnow only supports thedeveloperinstance; network docs are managed by editingnetwork_versions.jsondirectlyTest plan
yarn buildcompletes successfullyyarn startserves correctly with the new version configRELEASE_TYPEnode --test src/preprocess/__tests__/)🤖 Generated with Claude Code