chore(deps): bump the github-actions group across 1 directory with 5 updates#73
chore(deps): bump the github-actions group across 1 directory with 5 updates#73dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
…updates Bumps the github-actions group with 5 updates in the / directory: | Package | From | To | | --- | --- | --- | | [actions/checkout](https://github.com/actions/checkout) | `4` | `6` | | [actions/setup-go](https://github.com/actions/setup-go) | `5` | `6` | | [actions/upload-artifact](https://github.com/actions/upload-artifact) | `6.0.0` | `7.0.0` | | [docker/login-action](https://github.com/docker/login-action) | `3.6.0` | `3.7.0` | | [actions/attest-build-provenance](https://github.com/actions/attest-build-provenance) | `1.4.4` | `4.1.0` | Updates `actions/checkout` from 4 to 6 - [Release notes](https://github.com/actions/checkout/releases) - [Commits](actions/checkout@v4...v6) Updates `actions/setup-go` from 5 to 6 - [Release notes](https://github.com/actions/setup-go/releases) - [Commits](actions/setup-go@v5...v6) Updates `actions/upload-artifact` from 6.0.0 to 7.0.0 - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@b7c566a...bbbca2d) Updates `docker/login-action` from 3.6.0 to 3.7.0 - [Release notes](https://github.com/docker/login-action/releases) - [Commits](docker/login-action@5e57cd1...c94ce9f) Updates `actions/attest-build-provenance` from 1.4.4 to 4.1.0 - [Release notes](https://github.com/actions/attest-build-provenance/releases) - [Changelog](https://github.com/actions/attest-build-provenance/blob/main/RELEASE.md) - [Commits](actions/attest-build-provenance@ef24412...a2bbfa2) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: actions/setup-go dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: actions/upload-artifact dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: docker/login-action dependency-version: 3.7.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions - dependency-name: actions/attest-build-provenance dependency-version: 4.1.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
blob | 83c8604 | Commit Preview URL Branch Preview URL |
Mar 02 2026, 09:53 AM |
Kusari Analysis Results:Caution Flagged Issues Detected The dependency analysis found no issues. However, the code analysis identified two high severity supply chain risks in .github/workflows/go-mod-tidy.yml. Both actions/checkout@v6 (line 14) and actions/setup-go@v6 (line 19) use mutable version tags instead of immutable commit SHAs. This is especially concerning because the workflow runs with contents: write permissions and has access to secrets.REPO_PAT, meaning a tampered or silently updated action could exfiltrate secrets or manipulate repository contents without detection. The risk is compounded by the workflow triggering on pull requests, widening the attack surface. To proceed, both actions must be pinned to their full commit SHA (e.g., actions/checkout@<full-sha> and actions/setup-go@<full-sha>) to eliminate the supply chain risk before merging. Note View full detailed analysis result for more information on the output and the checks that were run. Required Code MitigationsPin actions/checkout to a full commit SHA instead of a mutable version tag (e.g., @v6). Using a mutable tag allows the action to be silently updated or replaced, introducing supply chain risk in a workflow with elevated repository permissions.
Pin actions/setup-go to a full commit SHA instead of a mutable version tag (e.g., @v6). Using a mutable tag allows the action to be silently updated or replaced, introducing supply chain risk.
Found this helpful? Give it a 👍 or 👎 reaction! |
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - uses: actions/checkout@v6 |
There was a problem hiding this comment.
Pin actions/checkout to a full commit SHA instead of a mutable version tag (e.g., @v6). Using a mutable tag allows the action to be silently updated or replaced, introducing supply chain risk in a workflow with elevated repository permissions.
| token: ${{ secrets.REPO_PAT }} | ||
|
|
||
| - uses: actions/setup-go@v5 | ||
| - uses: actions/setup-go@v6 |
There was a problem hiding this comment.
Pin actions/setup-go to a full commit SHA instead of a mutable version tag (e.g., @v6). Using a mutable tag allows the action to be silently updated or replaced, introducing supply chain risk.
Bumps the github-actions group with 5 updates in the / directory:
46566.0.07.0.03.6.03.7.01.4.44.1.0Updates
actions/checkoutfrom 4 to 6Release notes
Sourced from actions/checkout's releases.
... (truncated)
Commits
de0fac2Fix tag handling: preserve annotations and explicit fetch-tags (#2356)064fe7fAdd orchestration_id to git user-agent when ACTIONS_ORCHESTRATION_ID is set (...8e8c483Clarify v6 README (#2328)033fa0dAdd worktree support for persist-credentials includeIf (#2327)c2d88d3Update all references from v5 and v4 to v6 (#2314)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)08c6903Prepare v5.0.0 release (#2238)Updates
actions/setup-gofrom 5 to 6Release notes
Sourced from actions/setup-go's releases.
... (truncated)
Commits
4b73464Fix golang download url to go.dev (#469)a5f9b05Update default Go module caching to use go.mod (#705)7a3fe6cBump qs from 6.14.0 to 6.14.1 (#703)b9adafdBump actions/checkout from 5 to 6 (#686)d73f6bcREADME.md: correct to actions/checkout@v6 (#683)ae252eeBump@actions/cacheto v5 (#695)bf7446aBump js-yaml from 3.14.1 to 3.14.2 (#682)02aadfeFix Node.js version in action.yml (#691)4aaadf4Example for restore-only cache in documentation (#696)4dc6199Bump semver and@types/semver(#652)Updates
actions/upload-artifactfrom 6.0.0 to 7.0.0Release notes
Sourced from actions/upload-artifact's releases.
Commits
bbbca2dSupport direct file uploads (#764)589182cUpgrade the module to ESM and bump dependencies (#762)47309c9Merge pull request #754 from actions/Link-/add-proxy-integration-tests02a8460Add proxy integration testUpdates
docker/login-actionfrom 3.6.0 to 3.7.0Release notes
Sourced from docker/login-action's releases.
Commits
c94ce9fMerge pull request #915 from docker/dependabot/npm_and_yarn/lodash-4.17.238339c95Merge pull request #912 from docker/scopec83e932build(deps): bump lodash from 4.17.21 to 4.17.23b268aa5chore: update generated contenta603229documentation for scope input7567f92Add scope input to set scopes for the authentication token0567fa5Merge pull request #914 from dphi/add-support-for-amazonaws.euf6ef577feat: add support for AWS European Sovereign Cloud ECR registries916386bMerge pull request #911 from crazy-max/ensure-redact5b3f94achore: update generated contentUpdates
actions/attest-build-provenancefrom 1.4.4 to 4.1.0Release notes
Sourced from actions/attest-build-provenance's releases.
... (truncated)
Commits
a2bbfa2bump actions/attest from 4.0.0 to 4.1.0 (#838)0856891update RELEASE.md docs (#836)e4d4f7cprepare v4 release (#835)02a49bdBump github/codeql-action in the actions-minor group (#824)7c757dfBump the npm-development group with 2 updates (#825)c44148eBump github/codeql-action in the actions-minor group (#818)3234352Bump@types/nodefrom 25.0.10 to 25.2.0 in the npm-development group (#819)18db129Bump tar from 7.5.6 to 7.5.7 (#816)90fadfaBump@actions/corefrom 2.0.1 to 2.0.2 in the npm-production group (#799)57db8baBump the npm-development group across 1 directory with 3 updates (#808)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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions