Updating Changelog

Steps

1. Determine Target Files

Read .release-please-manifest.json to get the version (e.g., {"." : "4.0.0"} → edit v4.md).

Target files:

• Aztec contract developers: docs/docs-developers/docs/resources/migration_notes.md
• Node operators and Ethereum contract developers: docs/docs-operate/operators/reference/changelog/v{major}.md

2. Analyze Branch Changes

Run git diff next...HEAD --stat for overview, then git diff next...HEAD for details.

Categorize changes:

• Breaking changes (API modifications, removals, renames)
• New features (APIs, CLI flags, configuration)
• Deprecations
• Configuration changes (CLI flags, environment variables)

3. Generate Draft Entries

Present draft entries for review BEFORE editing files. Match the formatting conventions by reading existing entries in each file.

4. Edit Documentation

After approval, add entries to the appropriate files.

Migration Notes Format

File: docs/docs-developers/docs/resources/migration_notes.md

Add entries under ## TBD section:

markdown
1### [Component] Brief description
2
3Explanation of what changed.
4
5**Migration:**
6
7```diff
8- old code
9+ new code
10```

Impact: Effect on existing code.

Component tags: [Aztec.nr], [Aztec.js], [PXE], [Aztec Node], [AVM], [L1 Contracts], [CLI]

Node Operator Changelog Format

File: docs/docs-operate/operators/reference/changelog/v{major}.md

Breaking changes:

markdown
1### Feature Name
2
3**v{previous}:**
4```bash
5--old-flag <value>                    ($OLD_ENV_VAR)
6```
7
8**v{current}:**
9```bash
10--new-flag <value>                    ($NEW_ENV_VAR)
11```
12
13**Migration**: How to migrate.

New features:

markdown
1### Feature Name
2
3```bash
4--new-flag <value>                    ($ENV_VAR)
5```
6
7Description of the feature.

Changed defaults: Use table format with Flag, Environment Variable, Previous, New columns.