Bump actions/checkout from 5 to 6 #33
Open
Conversation
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
Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [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
dependabot
bot
requested review from
a team and
mmuller-tines
as code owners
dependabot
bot
added
the
github_actions
|
This pull request flags supply-chain risks in .github/workflows/test.yml where several GitHub Actions use floating/mutable tags (actions/checkout@v6, actions/setup-go@v6, golangci/golangci-lint-action@v8) and the linter is configured with version: latest, recommending pinning to exact release versions or commit SHAs to avoid unexpected or malicious changes. No secrets, elevated permissions, or insecure triggers were detected.
Supply Chain Risk in GitHub Actions in
|
| Vulnerability | Supply Chain Risk in GitHub Actions |
|---|---|
| Description | The GitHub Actions workflow uses a floating major version tag (actions/checkout@v6) for the checkout action. This practice introduces a supply chain risk because the code associated with the v6 tag can change over time without explicit review. A malicious update to the v6 tag by the action maintainers could lead to the execution of untrusted code within the CI/CD pipeline, potentially compromising the build environment, exfiltrating secrets, or injecting malicious code into the project's artifacts. |
go-sdk/.github/workflows/test.yml
Lines 14 to 17 in 286d3b2
Code Policy: GitHub Action Policy
| Policy | GitHub Action Policy |
|---|---|
| Result | Identified GitHub Actions Risks - Line 16: Uses third-party action golangci/golangci-lint-action@v8 via a mutable version tag. Pin to a specific commit SHA or exact release to reduce supply-chain risk. - Line 18: The linter is configured with version: latest, which fetches a rolling latest binary. This mutability can introduce unexpected changes; pin to a specific version. - Line 15: Uses first-party actions/checkout@v6 via a mutable tag. While first-party, pinning to a commit SHA or exact release is recommended to prevent unexpected updates. - Line 23: Uses first-party actions/checkout@v6 via a mutable tag. Same recommendation as above. - Line 24: Uses first-party actions/setup-go@v6 via a mutable tag. Prefer pinning to a commit SHA or exact release. No secrets usage, run: commands, permissions elevation, or insecure triggers are visible in this patch. |
go-sdk/.github/workflows/test.yml
Lines 11 to 25 in 286d3b2
All finding details can be found in the DryRun Security Dashboard.
krippee
approved these changes
Nov 25, 2025
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.
Bumps actions/checkout from 5 to 6.
Release notes
Sourced from actions/checkout's releases.
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
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)