[Nic-dorman]

No ## [X.Y.Z] section has been written since 0.3.6, so every tag from ant-cli-v0.3.7 to ant-cli-v0.3.12-rc.1 (five of them stable) shipped "No changelog entry was recorded …" as its release notes. This PR fills those sections in. #237 fixes the process that let it happen.

• Rotation. The six [Unreleased] entries move, with their text unchanged, to the release that first shipped them by tag ancestry:
  • npm distribution, the bundled-seed fallback and ant update under a package manager go to 0.3.8 (feat(npm): distribute the ant CLI via npm as @withautonomi/ant #192);
  • pointer transfer and majority fork reads go to 0.3.11 (feat(pointer): hand a pointer over for good, and read forks by majority #210);
  • SHA-256 reporting goes to 0.3.12 (feat(upload, manifest): report the uploaded file's SHA-256 and record it on manifest entries (V2-1564) #229).
• Backfill. 0.3.7, 0.3.9 and 0.3.10 recorded nothing; 0.3.8 and 0.3.11 were partial. Their entries are now written from the PRs each tag contains (git log ant-cli-vPREV..ant-cli-vX). Release-promotion PRs are left out, and CI and test-only PRs go under Internal.
• 0.3.12 covers feat(read): spread hot-record reads across the close group, and back off briefly from nodes that decline #225, feat(upload, manifest): report the uploaded file's SHA-256 and record it on manifest entries (V2-1564) #229, feat(browser): export manifests and recover pointer payments #230 and chore(deps): move rustls to 0.23.46 for four RustSec advisories #232. The same file goes onto rc-2026.10.3 in the companion PR docs(changelog): 0.3.12 notes for rc-2026.10.3 (same file as main) #239, so ant-cli-v0.3.12 ships real notes instead of the placeholder. Please merge that one before the train's sign-off.
• Dates are the stable releases' publish dates. 0.3.12 uses the rc.1 cut date, as 0.3.6 did.

For reviewers. The new entries were drafted from PR bodies and diffs. Please check those for your own PRs:

• @mickvandijke: feat(client): share native upload, payment recovery, and discovery with browser WASM #186, feat(browser): record-batch uploads and private DataMap reads #203, fix!: recover browser sessions and speed up native/WASM downloads #206, fix(browser): keep media playback streaming while records are discovered #209, perf(browser): query six peers per lookup round #211, feat(wasm)!: support large-file downloads and disk streaming #214, fix(browser): stop reusing WebRTC connections the browser reports failed #215, fix(browser): gather ICE candidates one connection at a time #216, feat(read): spread hot-record reads across the close group, and back off briefly from nodes that decline #225 and feat(browser): export manifests and recover pointer payments #230;
• @grumbach: feat(quote): declare the settlement version when requesting quotes #171, fix(upload): report the settlement refusal that stopped a merkle payment #195, feat(pointer): create, update, read and resolve pointers #200, fix(pointer): read back a completed write, and pay only for writes that can land #208, feat(pointer): hand a pointer over for good, and read forks by majority #210 and ci(release): ship licence texts and third-party notices with the ant CLI #213.

The breaking-change headings for #186, #206 and #214 are inferred from those PRs' descriptions. Any measured numbers quoted are the PRs' own.

After both PRs merge, the published bodies of 0.3.2–0.3.5, 0.3.7–0.3.11 and 0.3.12-rc.1 will be corrected with gh release edit. Only their "Detailed Changes" part changes.

Linear issue

Closes V2-1107

Risk tier

• T0 — docs / tooling / CI / pure UX-output. Repo CI only.
• T1 — client-only, no network-facing behavior change. CI + prod compat smoke.
• T2 — node/client logic with behavioral surface, no protocol/format/economics change. Dev testnet + ADR.
• T3 — protocol / storage format / payments / routing. T2 evidence + adversarial testing.

Compatibility

• Wire: none
• Storage: none
• API: none. CHANGELOG.md only.

Semver impact

• breaking
• feature
• fix

Test evidence

• All six existing [Unreleased] entries appear exactly once in the new file, byte-identical (checked by substring count). Everything from ## [0.3.6] down is unchanged.
• PRs were attributed to releases by tag ancestry (git log ant-cli-vPREV..ant-cli-vX), and the three feat(npm): distribute the ant CLI via npm as @withautonomi/ant #192 entries were confirmed with git log -S. Dates are taken from gh release view … publishedAt.
• The release workflow's extraction, run over the new file, returns a non-empty section for every version from 0.3.2 to 0.3.12.
• Merge-back: this branch and the companion PR change CHANGELOG.md to the same blob. git merge-tree of the two is clean, so the promote PR's merge of rc-2026.10.3 back into main has no changelog conflict.

New dependency

none

ADR

n/a

Mitigation / rollback

Revert. Release notes go back to the placeholder; no code or artifacts are affected.

🤖 Generated with Claude Code