Skip to content

chore(release): v1.1.0 — Milestone 8: i18n & post-release governance (M8.8)#78

Merged
danielPoloWork merged 2 commits into
masterfrom
chore/release-v1.1.0
Jun 14, 2026
Merged

chore(release): v1.1.0 — Milestone 8: i18n & post-release governance (M8.8)#78
danielPoloWork merged 2 commits into
masterfrom
chore/release-v1.1.0

Conversation

@danielPoloWork

Copy link
Copy Markdown
Owner

Summary

Release PR for v1.1.0 — closes Milestone 8 (Internationalization & Post-Release Governance), the first post-1.0 MINOR. Purely additive documentation and governance — the shipped library is unchanged from v1.0.x (no API/ABI/behaviour change).

Why a MINOR (per the M8.5 decision tree)

The change adds new surface (translated docs, the maintenance protocol, the consistency lint + CI gate) backward-compatibly; every existing consumer is unaffected and the static archive is byte-identical to v1.0.1. That is a textbook MINOR.

Changes

  • version.hpp1.1.0; the pool_smoke version-check TEST_CASE asserts the new components.
  • CHANGELOG.md[Unreleased] (M8.1–M8.7 + M8.9) rolled into ## [1.1.0] — 2026-06-14 under a Milestone 8 headline; fresh empty [Unreleased]; link references rewritten.
  • docs/releases/v1.1.0.md — the release notes release.yml consumes.
  • README.md — status badge (v1.0.1v1.1.0), status paragraph, milestone table (Milestone 8 → ✅ complete).
  • ROADMAP.md — 8.8 flipped + a closing session checkpoint (the planned roadmap, Milestones 0–8, is complete).

What's in Milestone 8

zh-Hans + ja documentation translations (English normative — ADR-0032 / ADR-0033), the post-release maintenance protocol (ADR-0034), and the agent-runnable consistency lint + CI gate + agent-contract wiring (ADR-0035). Four ADRs (0032–0035) → 35 total.

Verification

  • Builds cleanly on the full toolchain matrix — only the version constants + the matching test assertion changed in source.
  • pool_smoke built and run locally (MSVC 19.51 + Ninja): the 1.1.0 version-check passes; CMake configured project(... VERSION 1.1.0).
  • Consistency lint run per the M8.7 obligation → OK (version lockstep across version.hpp / CHANGELOG / README badge / v1.1.0.md; README ↔ ROADMAP milestone agreement; i18n freshness; etc.).
  • markdownlint clean; the consistency CI job re-runs on this PR.

Documentation Impact

  • README.md — badge / status / milestone table.
  • ROADMAP.md — 8.8 + checkpoint.
  • ADR — N/A (release mechanics; M8's ADRs already landed).
  • Spec — N/A.
  • CHANGELOG.md — sealed [1.1.0] block.
  • Consistency lint passes — python tools/consistency_lint.py.

After merge (the release ritual)

  1. Maintainer reviews & merges.
  2. Agent tags v1.1.0 from master (ADR-0008); release.yml builds the per-platform tarballs + SHA256SUMS and drafts the Release from docs/releases/v1.1.0.md.
  3. Maintainer clicks Publish.

danielPoloWork and others added 2 commits June 14, 2026 19:10
…(M8.8)

Closes ROADMAP item 8.8 and Milestone 8 — the first post-1.0 MINOR. Purely
additive documentation/governance; the library binary is unchanged from v1.0.x.

- version.hpp -> 1.1.0; pool_smoke version-check updated (verified locally:
  pool_smoke passes).
- CHANGELOG.md [Unreleased] (M8.1-M8.7 + M8.9) rolled into [1.1.0] — 2026-06-14
  with a Milestone 8 headline; fresh empty [Unreleased]; link references rewritten.
- docs/releases/v1.1.0.md added (release.yml body).
- README badge (v1.0.1 -> v1.1.0), status paragraph, milestone table (M8 ->
  complete) refreshed.
- ROADMAP 8.8 flipped + a closing session checkpoint (planned roadmap complete).

Classified MINOR per the M8.5 decision tree (additive surface, no API/ABI/
behaviour change). Consistency lint run per the M8.7 obligation: OK. After merge,
the agent tags v1.1.0 from master (ADR-0008) and the maintainer publishes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The v1.1.0 release edits the English README (badge / status / milestone table),
which the consistency lint correctly flags as making the zh-Hans + ja README
translations stale relative to their recorded source commits. Squash-merge means
the resulting commit SHA cannot be pinned from within this PR, so the honest state
is `stale`: the manifest's two README rows flip translated -> stale here, and a
small follow-up PR (after v1.1.0 merges, when the source SHA exists) re-syncs the
README status sections and re-pins them to translated. The four spec/patterns rows
are unaffected (this PR does not touch those sources) and stay translated.

This is the consistency lint doing exactly its job.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@danielPoloWork danielPoloWork merged commit 6dfd4e1 into master Jun 14, 2026
34 checks passed
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