docs: backport testnet v4.2.0 update + AI tooling trim (backport #22744)#22802
Open
AztecBot wants to merge 2 commits intobackport-to-v4-next-stagingfrom
Open
docs: backport testnet v4.2.0 update + AI tooling trim (backport #22744)#22802AztecBot wants to merge 2 commits intobackport-to-v4-next-stagingfrom
AztecBot wants to merge 2 commits intobackport-to-v4-next-stagingfrom
Conversation
- developer_version_config.json: take incoming bump (mainnet/testnet -> v4.2.0) - docs/networks.md: drop the Use Case Suitability table per upstream PR
critesjosh
approved these changes
Apr 27, 2026
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.
Backport of #22744 to
backport-to-v4-next-staging.Summary (from upstream PR)
developer_version_config.jsonmainnet/testnet tov4.2.0.aztec-claude-pluginmarketplace install block and its row from the Aztec/Noir tool reference table in the AI tooling guide (current source + the closest matching versioned snapshot).getting_started_on_testnet.md(current + versioned).docs/docs/networks.md.Conflict resolution
The automatic cherry-pick failed on:
docs/developer_version_config.json— HEAD hadmainnet: v4.2.0-aztecnr-rc.2,testnet: v4.1.0-rc.2. Resolved by taking the incomingv4.2.0for both (the upstream PR's intent).docs/docs/networks.md— The "Use Case Suitability" table existed only on HEAD. Resolved by dropping the table per upstream PR.Notes for reviewer
docs/developer_versioned_docs/version-v4.2.0/ai_tooling.mdandgetting_started_on_testnet.md. That path does not exist on this branch, so git's rename heuristic auto-merged the changes intoversion-v4.1.0-rc.2/(the closest match).version-v4.2.0-aztecnr-rc.2/ai_tooling.mdstill referencesaztec-claude-plugin— flag if you'd prefer the cleanup applied there instead.Test plan
yarn buildindocs/completes without errorsVERSION=4.2.0aztec-claude-pluginClaudeBox log: https://claudebox.work/s/c8425044cd859e4d?run=1