Skip to content

chore: back-merge v2.0.0 into dev - #937

Merged
Brad-Edwards merged 3 commits into
devfrom
main
Jul 27, 2026
Merged

chore: back-merge v2.0.0 into dev#937
Brad-Edwards merged 3 commits into
devfrom
main

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated back-merge of the v2.0.0 release commit (version bump + CHANGELOG) from main into dev, so dev stays in sync. main is ahead of dev only by the release commit (fast-forward). dev's required checks do not run on this bot-opened PR — merge it directly (admin).

@Brad-Edwards
Brad-Edwards merged commit 6f0c815 into dev Jul 27, 2026
11 checks passed
Brad-Edwards added a commit that referenced this pull request Jul 27, 2026
`check_identity_cutover` pinned CHANGELOG.md by whole-file digest, but
release-please rewrites that file on every release, inserting each new section
above the existing ones. The pin therefore goes stale at every release by
construction. It did at v2.0.0: PR #937 back-merged the release into `dev` with
the required `verify` check failing, and the failure was overridden rather than
fixed, leaving `dev` red on this gate.

Add a `generated-release-history` record class that matches how the file is
actually maintained. It pins the classified tail exactly and holds everything
written above it to the live-tree rule of zero retired identity occurrences, so
newly generated content carries no historical exemption. Editing or truncating
the tail still fails closed.

This is strictly stricter than the whole-file pin it replaces: the old rule
allowed any content anywhere in the file so long as the digest was re-recorded,
which is exactly the re-record-and-move-on habit that let the override stand.

Manifest schema moves to historical-identity-records/v3.

Refs #908
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