Closed
Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...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
stuckvgn
reviewed
Feb 7, 2026
Contributor
stuckvgn
left a comment
stuckvgn
left a comment
There was a problem hiding this comment.
🔒 Security & Privacy Review (AI-Generated)
Security Improvements:
- Supply Chain Security (Action Pinning): The workflow currently references the action by a mutable tag (
@v6). In high-threat environments protecting activist infrastructure, this introduces a supply chain risk if the tag is hijacked or pointed to malicious code.- Recommendation: Pin the action to its immutable full commit SHA (e.g.,
uses: actions/checkout@<COMMIT-SHA>). Dependabot can be configured to automate this viaversioning-strategy: increase-if-necessarycombined with groups or specific configurations.
- Recommendation: Pin the action to its immutable full commit SHA (e.g.,
Security Notes:
- Enhanced Credential Protection: The upgrade to
v6is a positive security step. The change inpersist-credentialsbehavior (storing credentials in a separate file under$RUNNER_TEMPinstead of.git/config) significantly reduces the risk of authentication tokens being leaked to untrusted scripts or subsequent steps in the pipeline. - Audit Capability: Continued support for
fetch-depth: 0ensures that thegitleaksscanner can access the full commit history. This is essential for detecting secrets hidden in previous commits, maintaining the integrity of your anti-surveillance measures.
stuckvgn
reviewed
Feb 7, 2026
Contributor
stuckvgn
left a comment
stuckvgn
left a comment
There was a problem hiding this comment.
⚡ Performance & Scale Review (AI-Generated)
Performance Notes:
No performance concerns identified with the upgrade to actions/checkout@v6.
- Runtime Verification: Validated that
actions/checkout@v6uses the Node.js 24 runtime. This upgrade ensures continued performance support and aligns with active LTS execution environments, preventing potential degradation associated with deprecated runtimes. - Scalability Observation (Existing Pattern): The workflow retains
fetch-depth: 0(fetching full git history). While fully supported in v6, full history checkout is an O(n) operation that linearly degrades as the repository functionality grows. For a documentation repo, this is manageable now, but if the repo scales significantly, consider implementing a strategy to only fetch compariable commits forgitleaksto optimize pipeline duration.
stuckvgn
reviewed
Feb 7, 2026
Contributor
stuckvgn
left a comment
stuckvgn
left a comment
There was a problem hiding this comment.
🛡️ Correctness & Reliability Review (AI-Generated)
⚠️ Potential Reliability Issue: Credential Persistence Change
The upgrade to actions/checkout@v6 introduces a significant change in how git credentials are handled:
Credential Security: The
persist-credentialsfeature now stores credentials in a separate file under$RUNNER_TEMPinstead of writing them directly into.git/config.
Why this matters for Gitleaks:
Workflows named gitleaks.yml typically run the Gitleaks scanner, often as a Docker container action.
- Docker Compatibility: If the Gitleaks action attempts to run git commands that require authentication (or expects the token to be present in
.git/config), it may fail inside the container because standard Docker actions don't automatically see the new$RUNNER_TEMPcredential file unless the runner version is v2.329.0+. - Silent Failure Risk: If the scanner cannot access the git configuration or history correctly due to this change, it might default to scanning the current checkout without history, or fail to report errors loudly, leading to a "green" build that didn't actually scan the history.
🔍 Verification Required
Please verify the CI logs for this run confirm that:
- The
checkoutstep succeeds withfetch-depth: 0. - The Gitleaks step explicitly logs that it is scanning the expected number of commits (not just 0 or 1).
If the scanner runs as a binary (not Docker) or doesn't need to fetch/authenticate, this change is safe. However, given the "Silent failures mean activists think they're making impact when they're not" mandate, we must verify the scanner is actually seeing the data.
Author
|
Looks like actions/checkout is no longer a dependency, so this is no longer needed. |
dependabot
bot
deleted the
dependabot/github_actions/actions/checkout-6
branch
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 4 to 6.
Release notes
Sourced from actions/checkout's releases.
... (truncated)
Changelog
Sourced from actions/checkout's changelog.
... (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)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 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)