Add composite action to Dependabot config#4773
Conversation
e13ad01 to
38a8cb1
Compare
Dependabot's github-actions ecosystem with directory "/" only scans .github/workflows/, not .github/actions/. This caused the composite action's pinned dependencies to drift behind the workflow files. Use "directories" (plural) to include both locations in a single entry and align the stale pins with the current workflow versions. Co-authored-by: Isaac
38a8cb1 to
f01ce7f
Compare
|
Commit: f01ce7f
18 interesting tests: 9 SKIP, 6 RECOVERED, 3 flaky
Top 20 slowest tests (at least 2 minutes):
|
simonfaltum
left a comment
There was a problem hiding this comment.
Review (automated, 2 agents)
Verdict: Approved
0 Critical | 0 Major | 0 Gap | 1 Nit | 0 Suggestion
See inline comment for details.
|
|
||
| - name: Setup Go | ||
| uses: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00 # v6.0.0 | ||
| uses: actions/setup-go@4b73464bb391d4059bd26b0524d20df3927bd417 # v6.3.0 |
There was a problem hiding this comment.
[Nit] setup-go bumped to v6.3.0 here, but direct workflow calls are on v6.2.0
This updates setup-go from v6.0.0 to v6.3.0, but 6 jobs across 4 workflow files (check.yml, push.yml, release.yml, release-snapshot.yml) call actions/setup-go directly at v6.2.0. After this PR, jobs using the composite action get v6.3.0 while those calling setup-go directly stay on v6.2.0.
Low practical impact since dependabot will now manage both locations going forward.
Suggestion: Either pin to v6.2.0 here to truly align, or bump the direct workflow calls to v6.3.0 in this PR.
|
Commit: 66ff507
79 interesting tests: 28 MISS, 16 RECOVERED, 14 flaky, 12 KNOWN, 6 FAIL, 2 PANIC, 1 SKIP
Top 50 slowest tests (at least 2 minutes):
|
Summary
github-actionsecosystem withdirectory: "/"only scans.github/workflows/, not.github/actions/subdirectories. This caused the composite action's pinned action versions to drift behind the workflow files.directories(plural) to include both.github/workflows/and.github/actions/setup-build-environment/in a single Dependabot entry, so future bumps produce a single PR covering both locations.setup-go,setup-uv,ruff-action) with the current workflow versions.Test plan
This pull request was AI-assisted by Isaac.