What problem does it solve?
Keeps Aztec network/operator documentation accurate for each mainnet or testnet release by automatically pulling the latest version and contract addresses from the provided JSON-RPC endpoint, then rebuilding and versioning the operator docs without changing developer documentation.
Core Features & Use Cases
- Detects the correct release type (mainnet vs testnet) from the node version string returned by the RPC, and aborts on devnet/nightly usage.
- Regenerates and snapshots operator documentation by updating network and contract address tables, optionally incorporating operator content changes, regenerating the versioned Node JSON-RPC API reference, and producing a versioned docs snapshot.
- Updates network version configuration and cleans old versions so versioned docs mappings remain consistent on
next.
- Use case: You are preparing a new mainnet or testnet release and need contract address updates plus regenerated network/operator docs for the new tag, while leaving developer docs untouched.
Quick Start
Run the release-network-docs skill with your target node RPC URL to update, build, validate, and cut versioned network/operator documentation for that release.
