[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 (six 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. ant-cli-v0.3.12 shipped on 10-23 with the placeholder, before the companion PR for rc-2026.10.3 (docs(changelog): 0.3.12 notes for rc-2026.10.3 (same file as main) #239, now closed) could merge. Its published notes are corrected along with the others below.
• 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 this PR merges, the published bodies of 0.3.2–0.3.5, 0.3.7–0.3.11, 0.3.12-rc.1 and 0.3.12 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: no longer applies. The companion PR for rc-2026.10.3 (docs(changelog): 0.3.12 notes for rc-2026.10.3 (same file as main) #239) was closed after 0.3.12 shipped, so this PR is the only change to CHANGELOG.md here.

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

[MaidSafe-Hermes]

APPROVE. Reviewed commit 48de73a.

I verified all 30 cited PR merge commits are ancestors of the release tags listed in the changelog. The release dates match GitHub release metadata, including the documented rc.1 date convention for 0.3.12. The #237 release extractor returns non-empty notes for every version from 0.3.2 through 0.3.12 and for 0.3.12-rc.1. I also checked the cited source for the breaking API and RustSec statements. I found no material correction.

Coverage: 2/2 seats reviewed (sol-1 gpt-6.1-sol xhigh; glm-1 z-ai/glm-5.3). GLM approved. Sol-1 was uncertain because it could not verify every technical claim from the initial evidence. I checked the release ancestry and dates, extractor, and the material API/security claims it raised; no material objection remains. This is not model consensus.

Required checks linear-link and pr-template pass; self-test also passes on the latest run. The older full run had a Security Audit failure and a cancelled macOS Merkle E2E. This changelog-only diff changes no lockfile or code. Those older results are not required checks, but the full suite was not rerun on this head.

Approval is not a merge authorization.