githubnext / githubnext/gh-aw-cao
[dependabot:release-train-updater] Pin actions/checkout@v6 to SHA in 3 workflows (review bundle available)
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
### Control Plane
- Correlation ID: 33826174736-81
- Central repo: githubnext/gh-aw-cao
- Run URL: https://github.com/githubnext/gh-aw-cao/actions/runs/33826174736
- Target repository: `githubnext/gh-aw-workshop` (review mode — no direct target mutation performed)
## Summary
In `githubnext/gh-aw-workshop`, three workflow files still reference the mutable tag `actions/checkout@v6`, while five other workflows in the same repository already use the SHA-pinned `actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1`:
- `.github/workflows/copilot-setup-steps.yml`
- `.github/workflows/image-link-check.yml`
- `.github/workflows/no-see-also.yml`
## Why this matters
Mutable tags (`@v6`) are a supply-chain risk — the tag can be repointed to different code without review. Pinning to the SHA already vetted and used elsewhere in this repo closes that gap and removes drift/inconsistency.
## Proposed fix
Replace `uses: actions/checkout@v6` with `uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1` in the three files above. This is a 3-line, single-action-reference change — low risk, no runtime/build impact, CI-only.
## Validation performed
- YAML syntax validated for all three files after applying the change (parses cleanly).
- Could not reach the network from this sandbox to independently re-verify the SHA against the upstream `actions/checkout` release metadata; the SHA was cross-checked against the identical pin already present and running successfully in 5 other workflows in this same repository.
## Review bundle
A full review bundle (patch diff, changed-files list, validation output, and this summary) was published as a workflow artifact since this run operates in `review` mode against the control-plane repository (`githubnext/gh-aw-cao`), not directly against the target repository. A human with write access to `githubnext/gh-aw-workshop` should apply the patch and open the PR there, or re-run this workflow in `live` mode with authority for that target.
Smart-Dependabot-Merge-Candidate: yes (low risk, high confidence, no security concern, clean validation)
> Generated by [:dependabot: Dependabot / Release Trains](https://github.com/githubnext/gh-aw-cao/actions/runs/33826174736) · copilot · auto · 45.1 AIC · ⌖ 13.4 AIC · ⊞ 20.3K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-cao%2Fdependabot-release-train-updater%22&type=issues)
>
Add this agentic workflow to your repo
To install this agentic workflow, run
```
gh aw add githubnext/gh-aw-cao/.github/workflows/dependabot-release-train-updater.md@main
```
> - [x] expires on Sep 18, 2026, 1:40 AM UTC
Contributor guide
Research direction
Update .github/workflows/copilot-setup-steps.yml, image-link-check.yml, and no-see-also.yml in githubnext/gh-aw-workshop. Replace each actions/checkout@v6 reference with the specified SHA and v7.0.1 comment, then validate the three workflow files as YAML; done means all three use the existing repository-wide pin consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 92/100