fix: normalize standards-version marker in CLAUDE.md to 1.9.0#17
Merged
Conversation
Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.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
Sets
CLAUDE.mdstandards-versionmarker from1.9.4to1.9.0to match the value already carried byAGENTS.md, allskills/*/SKILL.mdfiles, and allrules/*.mdcfiles.Root cause
CLAUDE.mddid not exist in this repo at the time of the original fleet-wide alignment at1.9.0. It was added later via PR #15 ("fix: backfill CONTRIBUTING.md and CLAUDE.md per ecosystem standards"), which used the then-current meta-repoVERSION(1.9.4) as the stamp value. All other agent files had already been stamped at1.9.0in the earlier pass, creating an internal inconsistency within the repo.This is not a bug in
release-doc-syncor any script. Release-doc-sync does not touchstandards-versionmarkers (DTD#1). The inconsistency was a one-off from backfilling a missing file at a different point in time.What changes
CLAUDE.mdline 1:<!-- standards-version: 1.9.4 -->changed to<!-- standards-version: 1.9.0 -->After this merge
This repo will have uniform
standards-version: 1.9.0across all agent files. A full re-stamp to the current meta-repo VERSION is a separate fleet-wide rollout decision deferred to the maintainer.The
fix:prefix will drive a patch version bump on merge viarelease.yml. That is expected and correct.Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com