Skip to content

chore: release v0.25.0 - #242

Merged
mmcky merged 2 commits into
mainfrom
chore/release-v0.25.0
Aug 4, 2026
Merged

chore: release v0.25.0#242
mmcky merged 2 commits into
mainfrom
chore/release-v0.25.0

Conversation

@mmcky

@mmcky mmcky commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Release PR for v0.25.0. Promotes [Unreleased][0.25.0] - 2026-08-04 and bumps version references.

What ships (full detail in the CHANGELOG):

Change PR(s)
Security: \translate-resync trust gate in every workflow template + scaffolder #192 (#219)
Bibliography backfill — citations a sync introduces carry their entries across #117 (#226)
Review mode handles deliberate deletions instead of failing every language #210 (#214)
E2E harness tests one version across all nine workflows, gains ml, stops destroying fa workflows #202 (#206, #209)
ml packet rulings — register rules rewrite + glossary v0.2.0 #237
fr editor feedback — 4 register/anti-calque rules + glossary v1.1 #241

Pre-flight done on this branch: 1478/1478 tests green; npm run build leaves dist-action/index.js byte-identical (bundle already current — engineVersion reads package.json at runtime, so the version bump needs no rebuild). Glossary counts in docs/index.md corrected against the shipped files (fr 367, ml 57).

After merge (per the AGENTS.md release checklist): tag v0.25.0, E2E-gate the tag (§4a), then move v0.25/v0, smoke @v0, and create the GitHub release. Merging this PR alone ships nothing.

🤖 Generated with Claude Code

Promote [Unreleased] → [0.25.0] - 2026-08-04: the #192 trust-gated workflow
templates, #117 demand-driven bibliography backfill, #210 deletion
partitioning in review mode, the #202 one-version E2E harness, #237 ml
packet rulings, and #241 fr editor rules + glossary v1.1.

Version refs bumped (package.json, README, docs/index, architecture,
AGENTS.md release-gate example); glossary counts in docs/index corrected
against the shipped files (fr 364 → 367, ml 52 → 57); STATE.md release
entry added. Bundle verified byte-current before the bump — engineVersion
is read from package.json at runtime, so no rebuild rides this commit.
Copilot AI review requested due to automatic review settings August 4, 2026 01:35

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Release prep for v0.25.0, updating the repository’s published version markers and release documentation to reflect the new release date/version.

Changes:

  • Bump version to 0.25.0 across package.json, package-lock.json, and the primary version callouts in docs/README.
  • Promote the changelog entry from [Unreleased] to [0.25.0] - 2026-08-04.
  • Update release/checklist documentation (AGENTS.md, .dev/STATE.md) and glossary counts in docs/index.md.

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
README.md Update displayed version badge/text to v0.25.0.
package.json Bump package version to 0.25.0.
package-lock.json Keep lockfile metadata version in sync with 0.25.0.
docs/index.md Update docs landing page version and glossary term counts.
docs/developer/architecture.md Refresh “Last Updated” to v0.25.0 release date.
CHANGELOG.md Promote release notes to [0.25.0] - 2026-08-04.
AGENTS.md Update release-gate example command to v0.25.0.
.dev/STATE.md Mark #210 as released in v0.25.0 and add a v0.25.0 “Recently landed” entry.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread CHANGELOG.md
Comment thread .dev/STATE.md Outdated
Comment thread AGENTS.md
Comment thread .dev/STATE.md Outdated
Three of Copilot's four comments on #242 held up; this addresses them.

.dev/STATE.md said "the release decision is taken — v0.24.0 is cut" in the same
file that now carries a v0.25.0 entry, and it claimed #210 was "released in
v0.25.0" when the tags are uncut and @v0 still resolves to v0.24.0. Both now
state the actual position: v0.25.0 is prepared, PR #242 is open, nothing is
tagged. The verified: header goes to 2026-08-04, since the file's own preamble
tells readers to trust it less as that date ages and this PR edits it.

The --action-ref gate examples in AGENTS.md and tool-test-action-on-github/
README.md had drifted apart (v0.25.0 and v0.24.0 respectively). Rather than bump
both again, they now use the vX.Y.Z placeholder that AGENTS.md:236 and
README.md:55 already use — the drift was structural, not a missed edit, so this
removes the per-release churn instead of resetting it.

Copilot's fourth comment, asking for an empty [Unreleased] header above the
release section, is declined: the v0.24.0 release commit (86e154c) also went
straight to its version header, so the convention here is that the release
commit consumes [Unreleased] and the next feature PR reintroduces it.

Tests: 1478 passed, 64 suites.
@mmcky
mmcky merged commit c74e3aa into main Aug 4, 2026
1 check passed
@mmcky
mmcky deleted the chore/release-v0.25.0 branch August 4, 2026 06:35
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.

2 participants