Upgrade straggler checkout refs and guard against action major drift - #81
Merged
Conversation
The version-spec, version-pin-drift, config-legacy, and config-invalid jobs were authored alongside the bulk @v7 upgrade and missed it, leaving four actions/checkout@v5 refs on main. A stale major silently reintroduces the Node 20 deprecation warning the upgrade was meant to remove, so add a CI job that fails on any outdated first-party action major. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 68570e12-150a-4762-bccc-6af2377d8531
This was referenced Aug 28, 2026
This was referenced Sep 5, 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.
What
Four
actions/checkout@v5refs survived onmainand are now@v7, plus a CI guard so this class of drift can't come back silently.Why
The
version-spec,version-pin-drift,config-legacy, andconfig-invalidjobs were authored in #77 alongside the bulk@v7upgrade in #78. The two landed in parallel, so the new jobs never got swept — they shipped on@v5.That matters beyond tidiness: a stale major silently reintroduces the Node 20 deprecation warning the upgrade existed to remove. A real regression wearing a green checkmark, which is the same failure shape as the labeler bug in #78.
The guard
New
action-major-driftjob fails on any outdated first-party action major, scoped touses:declarations specifically — an unscoped pattern matched the guard's own allowlist string and passed only by accident.Verified in both directions:
checkout@v5-> correctly fails, reporting the offending file and lineResult
checkout@v5refs: 4 -> 0. All 31 checkout refs on@v7, 32 jobs total.Closes #50
Closes #66