feat: decouple STANDARDS_VERSION from meta release VERSION#66
Merged
Conversation
Add STANDARDS_VERSION file (1.10.0) as the single source of truth for the ecosystem standards surface. The drift checker and scaffold now read this file instead of VERSION, so registry additions and other meta-repo releases no longer force a fleet-wide re-stamp. - Add STANDARDS_VERSION at repo root containing 1.10.0 - Update scripts/drift_check/cli.py to read STANDARDS_VERSION - Update scaffold/create-tool.py to stamp from STANDARDS_VERSION - Update standards/versioning.md to define both files and when each moves - Bump VERSION to 1.12.0 Signed-off-by: fOuttaMyPaint <154358121+TMHSDigital@users.noreply.github.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Signed-off-by: fOuttaMyPaint <154358121+TMHSDigital@users.noreply.github.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
STANDARDS_VERSIONfile at repo root (1.10.0) as the single source of truth for the ecosystem standards surfacescripts/drift_check/cli.pyto readSTANDARDS_VERSIONinstead ofVERSIONscaffold/create-tool.pyto stamp new repos fromSTANDARDS_VERSIONinstead ofVERSIONstandards/versioning.mdto define both files and the rule for when each movesVERSIONto 1.12.0Why
Registry additions (
feat:commits) were forcing a minor bump toVERSION, which caused the drift checker to compare tool repos against the new meta release number rather than the actual standards version. This created false positive drift errors across all 10 fleet repos every time a new tool was registered.With this change,
STANDARDS_VERSIONmoves only when the standards surface itself changes (new required elements, changed frontmatter schemas, new checks).VERSIONtracks meta-repo releases as before. The two numbers now move independently.Gate check
sync_from_registry.py --checkexits 0 locallySTANDARDS_VERSION(1.10.0) after this merge; fleet re-stamp to 1.10.0 follows in the next PR series