Skip to content

docs(changelog): 0.3.12 notes for rc-2026.10.3 (same file as main) - #239

Open
Nic-dorman wants to merge 1 commit into
rc-2026.10.3from
nic/v2-1107-changelog-0.3.12-rc
Open

Nic-dorman wants to merge 1 commit into
rc-2026.10.3from
nic/v2-1107-changelog-0.3.12-rc

Conversation

@Nic-dorman

Copy link
Copy Markdown
Member

Into rc-2026.10.3, for the 2026-10-22 train (V2-1682). CHANGELOG.md has no ## [0.3.12] section, so ant-cli-v0.3.12-rc.1 shipped placeholder notes. The stable ant-cli-v0.3.12 tag is cut on this branch, so it will do the same unless the section lands here before sign-off.

This PR writes the same CHANGELOG.md, byte for byte, as the main PR #238: the rotation, 0.3.7–0.3.11 backfilled, and ## [0.3.12] - 2026-10-22 covering #225, #229, #230 and #232. It is docs only and changes no crate or workflow. Because both branches end with the identical blob, the promote PR's merge-back into main is conflict-free (checked with git merge-tree).

If this cannot merge before the stable tag, nothing breaks: the stable release ships the placeholder, and I'll correct it with gh release edit.

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

No `## [X.Y.Z]` section was written after 0.3.6, so every tag from
ant-cli-v0.3.7 to ant-cli-v0.3.12-rc.1 shipped placeholder release notes.

- The six [Unreleased] entries move, text unchanged, to the release that
  first shipped them by tag ancestry: three to 0.3.8 (#192), two to 0.3.11
  (#210) and the SHA-256 entry to 0.3.12 (#229).
- 0.3.7, 0.3.9, 0.3.10 and 0.3.12, which recorded nothing, and the rest of
  0.3.8 and 0.3.11 are written from the PRs each tag contains
  (`git log ant-cli-vPREV..ant-cli-vX`). Release-promotion PRs are left out.
- Dates are the stable releases' publish dates; 0.3.12 is the rc.1 cut date,
  as 0.3.6 was.
- Nothing from `## [0.3.6]` down changes.

Refs V2-1107.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant