ci: bump the last checkout pin in ci.yml to v7 (completes #365) - #371
Merged
TheZupZup merged 1 commit intoAug 14, 2026
Conversation
The dependency-guard job was added to ci.yml after Dependabot generated the actions/checkout v5 -> v7 bump, so it arrived on this branch via the merge from main still pinned to @v5. That left actions/checkout split across two refs, which toolchain_pins_test.dart ("each third-party action is used at one ref across .github/") fails on. Same class as the dart-dependency-updates.yml reference fixed earlier — both new @v5 uses came in with #370. This is the last one; every actions/checkout use under .github/ is now @v7.
TheZupZup
marked this pull request as ready for review
August 14, 2026 12:41
TheZupZup
merged commit Aug 14, 2026
250252a
into
dependabot/github_actions/github_actions-640176b5ab
7 checks passed
TheZupZup
added a commit
that referenced
this pull request
Aug 14, 2026
* ci: bump actions/checkout in / Bumps [actions/checkout](https://github.com/actions/checkout) in `/` from 5 to 7. Updates `actions/checkout` from 5 to 7 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v5...v7) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github_actions ... Signed-off-by: dependabot[bot] <support@github.com> * ci: keep checkout pin consistent * ci: bump the last checkout pin in ci.yml to v7 (#371) The dependency-guard job was added to ci.yml after Dependabot generated the actions/checkout v5 -> v7 bump, so it arrived on this branch via the merge from main still pinned to @v5. That left actions/checkout split across two refs, which toolchain_pins_test.dart ("each third-party action is used at one ref across .github/") fails on. Same class as the dart-dependency-updates.yml reference fixed earlier — both new @v5 uses came in with #370. This is the last one; every actions/checkout use under .github/ is now @v7. Co-authored-by: Claude <noreply@anthropic.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: TheZupZup <16434778+TheZupZup@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.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
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.
Targets #365's branch so the fix lands inside that PR and keeps it self-consistent.
What was actually failing
Not
flutter analyze— that step passes on #365's current head (7912ebe):The
Flutter checksjob fails one step later, influtter test:The single failure is the pin guardrail,
test/tooling/toolchain_pins_test.dart:188("shared GitHub Actions are pinned consistently → each third-party action is used at
one ref across
.github/"):Root cause
.github/workflows/ci.yml:102— theCheckoutstep of thedependency-guardjob —was still on
actions/checkout@v5.That job did not exist when Dependabot generated the bump (
25a5ce8). It was added toci.ymllater by #370 (75e548a), which introduced two fresh@v5checkout uses: onein the new
.github/workflows/dart-dependency-updates.ymland one in this newci.ymljob. Merging main into the Dependabot branch (
4150745) brought both onto the PR. Thefollow-up commit
7912ebe("ci: keep checkout pin consistent") fixed thedart-dependency-updates.ymlreference but missed theci.ymlone, soactions/checkoutstayed split across two refs and the guardrail kept failing.
Scope
This is specific to #365, not a pre-existing problem on
main. Onmainall 17actions/checkoutuses are@v5— one ref, so the guardrail passes there, and CI onmain(a2deeef) is green. The mixed set only exists on the update branch, which isexactly the drift the guardrail is designed to catch.
Change
One line,
.github/workflows/ci.yml:Every
actions/checkoutuse under.github/is now@v7, and every other third-partyaction resolves to a single ref (
setup-java@v5,setup-python@v7,upload-artifact@v7,download-artifact@v8,flutter-action@v2,rust-toolchain@stable,codex-action@v1).Not changed
flutter analyzeweakening — analyze was already clean.toolchain_pins_test.dartand the other guardrails are untouched; the fix satisfiesthe guardrail rather than relaxing it.
flutter-ci-fixer.ymlstill skipsdependabot/*anddeps/*branches, in both thefixjob and the publish-job restatement.actions/checkoutv5 → v7 update.Generated by Claude Code