chore: bump standards-version signals and drift-check pin to 1.9.0#18
Merged
TMHSDigital merged 2 commits intomainfrom Apr 26, 2026
Merged
chore: bump standards-version signals and drift-check pin to 1.9.0#18TMHSDigital merged 2 commits intomainfrom
TMHSDigital merged 2 commits intomainfrom
Conversation
Contributor
Dependency ReviewThe following issues were found:
License Issues.github/workflows/drift-check.yml
OpenSSF Scorecard
Scanned Files
|
Aligns with the meta-repo's v1.9.0 release (DTD#12 stale-counts policy correction shipped 2026-04-25). Per Phase 2 Decision 1 (same-major-minor signal granularity), tool repos should track the meta-repo's current MINOR. Two coordinated changes: 1. Bumps standards-version from 1.7.0 to 1.9.0 across all SKILL.md, .mdc, AGENTS.md (where present), and CLAUDE.md (where present) files in this repo. Eliminates the 2-minor drift that has been showing as version-signal errors in this repo's drift-check workflow runs. 2. Bumps the drift-check composite-action pin in .github/workflows/drift-check.yml from @v1.7 to @v1.9. The action carries the meta-repo VERSION it ships with; the @v1.7 pin compared this repo's signals against an older meta-version, surfacing the bumped tool signals as inverse-direction warnings. Pinning to @v1.9 (DTD#14 floating tag) keeps the comparison aligned within the current MINOR. Refs TMHSDigital/Developer-Tools-Directory#12. Signed-off-by: TMHSDigital <154358121+TMHSDigital@users.noreply.github.com> Made-with: Cursor
TMHSDigital
force-pushed
the
chore/bump-standards-version-to-1.9.0
branch
from
a85e77d to
55d73fc
Compare
TMHSDigital
changed the title
TMHSDigital
added a commit
to TMHSDigital/Developer-Tools-Directory
that referenced
this pull request
Apr 26, 2026
The `meta-repo-ref` default in .github/actions/drift-check/action.yml was hardcoded to 'v1.7' and never updated when 1.8 and 1.9 shipped. Tool repos consuming the action without explicit override would get the meta-repo checked out at v1.7 regardless of which version of the action they pinned, producing inverse-direction version-signal drift if their signals ever moved past 1.7.0. Fixes by changing the default to 'v1' (the auto-maintained MAJOR floating tag per DTD#14). Future MINORs auto-flow through this default without requiring action.yml edits. Surfaced during the v1.7.0 -> v1.9.0 ecosystem signal rollout when the Home-Lab canary's drift-check failed with 35 inverse-direction warnings: tool signals at 1.9.0 vs action's hardcoded v1.7 meta-VERSION. Adds regression test asserting the default matches floating-major pattern (v[0-9]+) to prevent re-introduction. Refs TMHSDigital/Home-Lab-Developer-Tools#18. Made-with: Cursor Signed-off-by: TMHSDigital <154358121+TMHSDigital@users.noreply.github.com>
Made-with: Cursor
This was referenced Apr 26, 2026
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.
Bumps standards-version signals from 1.7.0 to 1.9.0 to align with the meta-repo's current MINOR, and bumps the drift-check action pin from
@v1.7to@v1.9so the composite action's bundled meta-VERSION matches the bumped signals.Per Phase 2 Decision 1 (same-major-minor signal granularity), tool repos should track the meta-repo's MINOR. The meta-repo shipped 1.8.0 (release-doc-sync), 1.8.x patches, and 1.9.0 (DTD#12 stale-counts policy) since this repo last bumped.
The drift-check workflow on this repo has been reporting version-signal errors due to the gap. Bumping signals alone is not enough: the composite-action pin carries its own copy of the meta VERSION, so leaving
@v1.7would surface the freshly-bumped signals as inverse-direction warnings. Bumping the pin to@v1.9(the floating tag DTD#14 maintains for the current MINOR) keeps both sides aligned.Refs TMHSDigital/Developer-Tools-Directory#12.