docs(release): cut 3.7.0 — PRINCIPLE, catalogue boundary, admission-record fields - #512
Merged
Conversation
…ecord fields Categorises the commits landed since #493's 3.6.0 tag per RELEASING.md's bump table. Highest is a set of purely additive schema changes: the new PRINCIPLE codex TYPE, the new introduced_in relation kind, and the new CAT-001/CAT-002/ADMIT-009/ADMIT-010/ADMIT-011 validator codes -> MINOR. CONTRACT §10.4's grandfather clause (a MINOR/PATCH release's new error-severity rules apply only to files authored against that release or later) keeps CAT-002 and the INFORMATION_ENTITY BOBJ-D001 severity correction from forcing a MAJOR bump. Backfills five CHANGELOG entries for PRs that shipped without their own (the CAT-001/CAT-002, ADMIT-009, ADMIT-010/ADMIT-011, introduced_in, and governance standing-grant changes), matching the pattern #493 used to fold un-notated PRs into a release. Bumps notations/CURRENT_VERSION.yaml and PRESETS_VERSION to 3.7.0 and mechanically re-pins methodology_version across the 51 files check-notations.mjs's V1 check flagged. Backfills last_updated/version frontmatter on the three specs (17-relations.md, 16-assertion.md, MANIFEST.md) edited since 3.6.0 without it, and adds PRINCIPLE to COVERAGE_PROFILES.md §2.1's codex-artefact list alongside its siblings. node scripts/check-notations.mjs clean (two pre-existing SIZE1 warnings, non-blocking); ingest-cli suite 135/135 green. Signed-off-by: transitrix <automation@transitrix.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
1 participant
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.
Summary
Cuts methodology 3.7.0, the release RELEASING.md's checklist calls for now that #511 (PRINCIPLE) merged. MINOR — every schema-shaped change since the 3.6.0 tag is additive (new
PRINCIPLEcodex TYPE, newintroduced_inrelation kind, newCAT-001/CAT-002/ADMIT-009/ADMIT-010/ADMIT-011codes); the two newerror-severity codes don't forceMAJORbecause CONTRACT §10.4's grandfather clause keeps them from applying retroactively to already-admitted adopter canon.[3.7.0]section with a bump-category rationale.notations/CURRENT_VERSION.yamlandPRESETS_VERSIONto3.7.0; mechanically re-pinsmethodology_versionacross the 51 filescheck-notations.mjs'sV1check flagged.version/last_updatedfrontmatter on the three specs edited since 3.6.0 without it (17-relations.md,16-assertion.md,MANIFEST.md), and addsPRINCIPLEtoCOVERAGE_PROFILES.md§2.1's codex-artefact list alongside its siblings.Test plan
node scripts/check-notations.mjs— clean (two pre-existingSIZE1warnings, non-blocking)node --test packages/ingest-cli/src/*.test.mjs— 135/135 greenv3.7.0is cut from the merged commit in a follow-up run, per RELEASING.md step 8Once tagged, this unblocks the acme-corp
PRINCIPLEworked example and its ADR-0006-style pin bump, the remaining piece of the PRINCIPLE epic.