chore: release v0.26.0 - #274
Merged
Merged
Conversation
Promote [Unreleased] -> [0.26.0] - 2026-08-17; bump package.json, package-lock.json, README, docs/index, architecture header; STATE.md release record. Payload since v0.25.0: the ml round-1 encoding (#272, verified by #273), verdict engineRef provenance (#247), writeConfig key preservation (#243), newline-terminated writers (#266/#267), pricing-table repair (#230), resync-gate startsWith alignment (#234), heading-map docs fix (#91), deprecation warning for legacy heading-map reads (#53), harness scenario 27. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Release PR for v0.26.0, promoting the changelog entries and updating version markers across the repo and developer state notes.
Changes:
- Bump version references to v0.26.0 (README, docs, package metadata).
- Promote CHANGELOG content to a 0.26.0 release section dated 2026-08-17.
- Update
.dev/STATE.md“In flight” to include the v0.26.0 release-cut entry.
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| README.md | Update displayed project version to v0.26.0. |
| package.json | Bump npm package version to 0.26.0. |
| package-lock.json | Align lockfile package version fields with 0.26.0. |
| docs/index.md | Update docs landing page “Current status” version to v0.26.0. |
| docs/developer/architecture.md | Refresh “Last Updated” header to v0.26.0 / 17 August 2026. |
| CHANGELOG.md | Promote [Unreleased] content into [0.26.0] - 2026-08-17. |
| .dev/STATE.md | Add v0.26.0 release-cut item to “In flight”. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…#274) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release PR for v0.26.0 — version bump, changelog promotion, and the STATE record; no engine-code changes beyond what is already on
main.Payload since v0.25.0 (full detail in CHANGELOG
[0.26.0]): the ml round-1 encoding — glossary v0.3.0 and the 18-rule set (#272), regeneration-verified (#273); verdictengineVersion/engineRefprovenance (#247);writeConfigunknown-key preservation (#243); newline-terminated init/forward writers (#266/#267); the pricing-table repair with new model patterns (#230); the resync-gatestartsWithalignment across all documented workflow copies (#234 item 4); the heading-map docs correction (#91); the legacyheading-map:read deprecation warning (#53); and harness scenario 27 (citation backfill, exercised against the deployed release).Verified on this branch:
npm test1516/1516 · lint ·format:check·dist-action/rebuilt.Post-merge §4a runbook (I'll drive it once this merges): tag
v0.26.0on the merge commit → E2E-gate the tagged bytes (test-action-on-github.sh --action-ref v0.26.0) → move floatingv0.26+v0→ smoke--action-ref v0 --scenarios 01→gh release create v0.26.0(notes drafted in.dev/scratch/release-notes-v0.26.0.md). Production editions pick up the ml rules the moment@v0moves.🤖 Generated with Claude Code