docs: restore two-crate testing guidance + /errors/1 anchor#23632
Merged
Conversation
AztecBot
added
claudebox
…rate anchor Re-adds the "Keep tests in the test crate" section to testing_contracts.md, restoring the #keep-tests-in-the-test-crate anchor that the /errors/1 redirect points to. Also fixes index.md and counter_contract.md, which still described `aztec new` as creating a single-crate project; the nightly/source docs track the two-crate `aztec new`/`aztec init` behavior.
AztecBot
changed the title
The v4.3.0 snapshot (the default/live docs version) still carried the stale single-crate text from c93f23b and lacked the #keep-tests-in-the-test-crate anchor, so /errors/1 was broken on the live site even though v4.3.0 ships the two-crate `aztec new` and the tests-in-contract-crate warning. Brings the v4.3.0 testing_contracts.md and index.md in line with the corrected source.
The `aztec new`/`aztec init` two-crate workspace, crate-naming, and `--name` removal changes shipped in v4.3.0 but were filed under "Unreleased (v5)" in the source migration notes, with no 4.3.0 section. Adds a `## 4.3.0` section and moves those three notes into it, matching the v4 branch's 4.3.0-rc.1 section and the v4.3.0 versioned docs snapshot. The Counter-template and DeployMethod.send entries stay under Unreleased (v5) (not in v4's 4.3.0 list).
nventuro
approved these changes
May 29, 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
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.
What
Fixes the orphaned
/errors/1anchor and the stale single-crate docs, in both the source (next/v5) docs and the live v4.3.0 versioned snapshot.Source docs (
docs-developers/, become live when v5 docs are cut):aztec-nr/testing_contracts.md— adds## Keep tests in the test crate(restores the#keep-tests-in-the-test-crateanchor the/errors/1redirect targets), on top of docs: update testing_contracts.md for two-crate aztec new layout #23617's two-crate## Basic test structure.aztec-nr/index.md— "Flow" step single-crate → two-crate.tutorials/contract_tutorials/counter_contract.md— prose single-crate → two-crate (matched its own tree).Live v4.3.0 versioned snapshot (
developer_versioned_docs/version-v4.3.0/, what docs.aztec.network serves today):4.
aztec-nr/testing_contracts.md— brought in line with the corrected source (two-crate + the anchor). This is the fix that makes/errors/1resolve on the live site.5.
aztec-nr/index.md— single-crate → two-crate (preserving the resolvedtag="v4.3.0").(
contract_structure.mdandcounter_contract.mdin the v4.3.0 snapshot were already two-crate.)Why
v4.3.0ships the two-crateaztec newand theaztec compile"tests in contract crate" warning (checkNoTestsInContractsincompile.tsat tagv4.3.0), which links to/errors/1→…/testing_contracts#keep-tests-in-the-test-crate. That anchor did not exist, and the v4.3.0 testing/index pages still described single-crate (stale text frozen byc93f23b3before #23617 fixednext). v4.3.0 is the configured mainnet+testnet docs version and the only versioned dir, so this is the live default. With no v4.4.0 release, the snapshot won't be refreshed from source before v5, so it is patched directly here.Base
merge-train/fairies(where #23617 already restored the two-crate## Basic test structure). A later workflow merges the train intonext; thedocs/subrepo then syncs toAztecProtocol/docsand deploys.Follow-up (not in this PR)
Migration notes have no
## 4.3.0section and the two-crate change is still filed under## Unreleased (v5). That mislabeling is why the v4.3.0 snapshot was cut with single-crate text. Worth adding a## 4.3.0note, but that's a separate change.