You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(scaffold): derive meta-repo action pins from VERSION (#72)
Workflow action refs in generated tool repos were hardcoded literals
(drift-check@v1.9, release-doc-sync@v1), so every newly scaffolded repo
was born pinned to a stale meta-repo train. Hand-correcting one repo
(Blender @v1.9 -> @v1.15) treated the symptom; the source kept minting
stale refs.
Derive all three pins from the live meta VERSION at generation time:
- drift-check -> @v{MAJOR}.{MINOR} (MAJOR.MINOR train)
- release-doc-sync -> @v{MAJOR} (MAJOR train)
- meta-repo-ref -> v{MAJOR}.{MINOR}.{PATCH} (full current release tag)
A repo scaffolded after any future meta release is now born current
instead of stale. The validate.yml scaffold regression checks and the
ci-cd.md drift-check pin example are likewise derive-from-current rather
than hardcoded. Also fixes a stale test that asserted the release-doc-sync
default was v1.0 (it is v1, the floating-major train, since #43).
Scope: newly generated repos only; existing-repo ref bumps remain the
periodic standards re-stamp's job.
Signed-off-by: fOuttaMyPaint <154358121+TMHSDigital@users.noreply.github.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Pin the action to the meta-repo's current `MAJOR.MINOR` floating tag, never `@main` and never an older hardcoded minor. The scaffold derives this pin from the meta-repo `VERSION` at generation time, so newly created repos are born current; bumping the pin in existing repos is the periodic standards re-stamp's job. The companion `release-doc-sync` action pins to the `MAJOR` train (`@v<MAJOR>`) by the same rule. See [`release-doc-sync.md`](release-doc-sync.md) for that action's pinning convention.
74
+
73
75
`mode: self` checks only the calling repo's checkout; no cross-repo token is needed. Findings at `info` severity are advisory. Findings at `error` or `warn` severity indicate real drift that should be addressed.
0 commit comments