Bump actions/checkout from 5 to 6 #1473
Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Commits](actions/checkout@v5...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
| egress-policy: audit | ||
|
|
||
| - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0 | ||
| - uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1 |
There was a problem hiding this comment.
@kou please note: although @dependabot intended to upgrade this action to v6 in this PR, the SHA-versioned lines (three in total, I think) were in fact updated to v5.0.1.
The more-recent Dependabot PR #1490 has fixed this and updated to v6.0.1 -- even so, I would not currently recommend mixing SHA-versioned and tag-versioned references to the same action within a single repository's GitHub Actions workflows.
There was a problem hiding this comment.
I think that the improved versioning comments in that PR are helpful. I'd add a caution, though, that, as I understand it, Dependabot alerts are not able to scan and issue vulnerability notices for actions referenced from workflow files using SHA1 referencing. I learned that from the somewhat-popular, yet-to-be-resolved discussion thread titled Please make Dependabot Alerts support SHA-hash-versioned GitHub Actions at: https://github.com/orgs/community/discussions/154189
Bumps actions/checkout from 5 to 6.
Release notes
Sourced from actions/checkout's releases.
Commits
1af3b93update readme/changelog for v6 (#2311)71cf226v6-beta (#2298)069c695Persist creds to a separate file (#2286)ff7abcdUpdate README to include Node.js 24 support details and requirements (#2248)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)