@v1 moving tag is stale (points at v0.1.1) and there is no real v1.x release
The README tells consumers to pin uses: Ndevu12/strix@v1 and says it "tracks the latest v1.x release." In practice:
@v1 currently resolves to v0.1.1's commit (e3c7e08…) — three tags behind the latest v0.1.4 (93fe465…).- There is no actual v1.x release; the whole line is
0.1.x. So @v1 neither tracks "latest" nor exists as a real major.
Impact
Fix options
- Either advance
@v1 to the latest release commit on every release (and keep it moving), or
- Drop the
@v1 guidance and document pinning a real @v0.1.x tag or a commit SHA (the README already recommends a SHA "in production" — make that the primary guidance).
Relates to Ndevu12/stayAwakeBot#1229 (saw guard will resolve + SHA-pin the latest real release).
@v1moving tag is stale (points at v0.1.1) and there is no real v1.x releaseThe README tells consumers to pin
uses: Ndevu12/strix@v1and says it "tracks the latest v1.x release." In practice:@v1currently resolves to v0.1.1's commit (e3c7e08…) — three tags behind the latestv0.1.4(93fe465…).0.1.x. So@v1neither tracks "latest" nor exists as a real major.Impact
@v1silently runs a stale action (missing everything since v0.1.1) while believing they're current.saw guard setup, feat(guard): saw guard setup / saw guard check — install & verify the Strix CI gate on a repo stayAwakeBot#1229) needs an honest ref to pin.Fix options
@v1to the latest release commit on every release (and keep it moving), or@v1guidance and document pinning a real@v0.1.xtag or a commit SHA (the README already recommends a SHA "in production" — make that the primary guidance).Relates to Ndevu12/stayAwakeBot#1229 (
saw guardwill resolve + SHA-pin the latest real release).