-
Notifications
You must be signed in to change notification settings - Fork 275
build(deps): consolidate dependency updates #3420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,7 +15,7 @@ jobs: | |
| id-token: write | ||
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v7.0.0 | ||
| uses: actions/checkout@v7.0.1 | ||
| with: | ||
| fetch-depth: 0 # Full history for commit analysis | ||
|
Comment on lines
17
to
20
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔒 Security & Privacy | 🟠 Major | ⚡ Quick win 🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -euo pipefail
echo "== files =="
git ls-files | rg '(^|/)\.github/workflows/update-onboarding-skill\.yml$|\.github/workflows/update-onboarding-skill\.yml' || true
echo "== target workflow =="
cat -n .github/workflows/update-onboarding-skill.yml | sed -n '1,220p'
echo "== search for action permissions/run behavior mentions =="
rg -n "permissions:|anthropics/claude-code-action|actions/checkout|persist-credentials|GITHUB_TOKEN|git push|gh " .github/workflows/update-onboarding-skill.yml .github/workflows || true
echo "== workflow syntax parse-ish line count =="
wc -l .github/workflows/update-onboarding-skill.ymlRepository: evstack/ev-node Length of output: 12956 🌐 Web query:
💡 Result: The anthropics/claude-code-action@v1 action handles Git authentication internally to allow Claude to perform Git operations (such as committing changes) without permanently embedding tokens in the repository configuration [1][2]. How it manages Git credentials: 1. Credential Helper Approach: The action typically configures a custom Git credential helper to manage authentication [1][2]. It creates a temporary helper script (e.g., named.git-credential-gh-token) alongside the action source [1][2]. This script is configured via Citations:
🌐 Web query:
💡 Result: In the Citations:
Disable persisted checkout credentials before running Claude. The checkout step persists the write-capable 🧰 Tools🪛 zizmor (1.28.0)[warning] 17-20: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false (artipacked) 🤖 Prompt for AI AgentsSource: Linters/SAST tools |
||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
github web search actions/checkout v7.0.1 commit 3d3c42e5aac5ba805825da76410c181273ba90b1💡 Result:
The Git commit hash 3d3c42e5aac5ba805825da76410c181273ba90b1 corresponds to the release of actions/checkout version v7.0.1 [1][2]. This commit, titled "prep v7.0.1 release (
#2531)," was authored on July 17, 2026, and the v7.0.1 release was officially published on July 20, 2026 [1][2]. This release included several updates and fixes, such as: * Skipping the unsafe pull request check if the input is set to the default [2]. * Trimming only ASCII whitespace for branch inputs [2]. * Escaping values passed to --unset [2]. * Various dependency updates [2]. You can view the specific commit details and the full changelog on the official GitHub repository for actions/checkout [1][2].Citations:
🏁 Script executed:
Repository: evstack/ev-node
Length of output: 3648
🌐 Web query:
site:github.com/actions/checkout 3d3c42e5aac5ba805825da76410c181273ba90b1 "prep v7.0.1 release"💡 Result:
The commit 3d3c42e5aac5ba805825da76410c181273ba90b1 in the actions/checkout GitHub repository represents the preparation for the v7.0.1 release [1]. This commit, titled "prep v7.0.1 release" and associated with pull request
#2531, was authored on July 17, 2026 [2][1]. The commit performed the following actions to prepare for the release: - Updated the version from 7.0.0 to 7.0.1 in package.json [2]. - Synchronized the package version fields in package-lock.json to 7.0.1 [2]. - Added a section for v7.0.1 to CHANGELOG.md [2].Citations:
Pin
actions/checkoutto the immutablev7.0.1commit.Replace
actions/checkout@v7.0.1with the pinned commit3d3c42e5aac5ba805825da76410c181273ba90b1in the workflows still using the mutable tag.🧰 Tools
🪛 zizmor (1.28.0)
[warning] 25-25: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
📍 Affects 8 files
.github/workflows/docker-tests.yml#L25-L25(this comment).github/workflows/docker-tests.yml#L45-L45.github/workflows/docker-tests.yml#L65-L65.github/workflows/docs_build.yml#L19-L19.github/workflows/docs_deploy.yml#L31-L31.github/workflows/docs_preview.yml#L24-L24.github/workflows/lint.yml#L15-L15.github/workflows/lint.yml#L40-L40.github/workflows/lint.yml#L49-L49.github/workflows/lint.yml#L63-L63.github/workflows/lint.yml#L78-L78.github/workflows/proto.yml#L14-L14.github/workflows/release-apps.yml#L27-L27.github/workflows/release-apps.yml#L78-L78.github/workflows/release-github.yml#L35-L35🤖 Prompt for AI Agents
🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: evstack/ev-node
Length of output: 5373
🌐 Web query:
actions/checkout persist-credentials default true README💡 Result:
In the actions/checkout GitHub Action, the persist-credentials input determines whether the authentication token or SSH key used for the checkout is configured with the local git configuration [1][2]. Key details regarding this setting include: Default Value: The default value for persist-credentials is true [1][2]. Purpose: When set to true (the default), the action persists the credentials in the local git configuration of the checked-out repository [1][3]. This allows subsequent git commands (such as git fetch, git push, or git pull) executed later in your workflow to run with authenticated access automatically [4][5]. Security Enhancement: In recent versions (v6.0.0 and later), the implementation of credential persistence was updated to store these credentials in a separate file under the $RUNNER_TEMP directory instead of directly modifying the.git/config file, which improves security [3][6]. The credentials are removed automatically during the post-job cleanup phase [1][3]. Opt-Out: If you do not want your credentials persisted, you can explicitly set persist-credentials to false in your workflow step [1][5]. This is often done to increase security if the workflow does not require further authenticated git operations [4].
Citations:
🏁 Script executed:
Repository: evstack/ev-node
Length of output: 21083
🌐 Web query:
actions/checkout persist-credentials true local git config /tmp runner credentials GitHub Actions💡 Result:
In GitHub Actions, the
persist-credentialsinput for theactions/checkoutaction controls whether the repository's authentication token (or SSH key) is configured in the local Git environment to allow subsequent Git commands in the workflow to run authenticated [1][2][3]. Evolution of Implementation: Historically,actions/checkoutconfigured the Git authentication token directly within the local.git/configfile [1][4]. However, starting withactions/checkoutv6.0.0, the implementation was updated to improve security [4][5]. Instead of writing the credentials directly into the local repository configuration, the action now stores them in a separate file located under$RUNNER_TEMPand uses Git'sincludeIfconditional configuration to reference them [4][5]. This change prevents the sensitive credentials from residing directly within the.git/configfile, which was previously a potential risk for accidental exposure [4][5]. Key Considerations: - Default Behavior: By default,persist-credentialsis set totrue[1][2]. - Functionality: Whentrue, it enables your workflow scripts to run authenticated Git commands (e.g.,git pushorgit pull) without requiring additional authentication steps [1][4][3]. - Cleanup: The authentication token is automatically removed by a post-job cleanup step once the job finishes [1][4]. - Security: Whilepersist-credentials: trueis the default, some users prefer setting it tofalseas a security best practice to minimize exposure if unnecessary [6][7]. If set tofalse, your workflow scripts will not have access to the repository's credentials via the Git configuration [1][3]. For scenarios involving Docker container actions, usingpersist-credentials(v6+) requires a minimum Actions Runner version of v2.329.0 to correctly access the credentials stored in$RUNNER_TEMP[4][5].Citations:
persist-credentials=trueplease actions/checkout#2312🌐 Web query:
actions/checkout persist-credentials false workflow authenticated git operations💡 Result:
In GitHub Actions, the persist-credentials input for the actions/checkout action controls whether the repository's authentication token (typically the GITHUB_TOKEN) is stored in the local Git configuration [1][2]. When persist-credentials is set to the default value of true, the action configures the runner's local Git environment with the necessary credentials to perform authenticated Git operations, such as git fetch or git push, throughout the remainder of the workflow job [1][2]. While convenient, this approach has historically been identified as a security risk because it leaves the credentials accessible to any subsequent step or third-party action in that same job [3][4]. If you set persist-credentials: false, the action will not store the authentication token in the Git configuration [1][3]. If your workflow requires performing authenticated Git operations later (such as a git push), you must manually authenticate Git within that specific step [4][5]. To perform authenticated Git operations when persist-credentials is false, you can explicitly configure the remote URL with the token in the step where the operation is needed [4][5]. An example of this pattern is: git remote set-url origin "https://x-access-token:${{ secrets.GITHUB_TOKEN }}
@github.com/${{ github.repository }}.git" git push This approach ensures that credentials are only present and active during the exact step that requires them, rather than being persisted for the entire duration of the job [4][5]. Recent versions of actions/checkout have also improved security by storing these credentials in a more restricted location (under $RUNNER_TEMP) rather than directly in.git/config, though explicitly setting persist-credentials to false remains a recommended practice for hardening workflow security [2][3][6].Citations:
persist-credentials=trueplease actions/checkout#2312Disable checkout credential persistence unless the job needs authenticated Git access.
actions/checkoutpersists the repo token by default. Addpersist-credentials: falseto these checkout steps unless a later step needs authenticatedgitcommands:.github/workflows/docker-tests.ymllines 25, 45, 65.github/workflows/docs_build.ymlline 19.github/workflows/docs_deploy.ymllines 31-33 (add to the existingwithblock).github/workflows/lint.ymllines 15, 40, 49-51, 63-65, 78-80.github/workflows/proto.ymlline 14.github/workflows/release-apps.ymllines 27, 78.github/workflows/release-github.ymllines 35-37🧰 Tools
🪛 zizmor (1.28.0)
[warning] 25-25: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
📍 Affects 7 files
.github/workflows/docker-tests.yml#L25-L25(this comment).github/workflows/docker-tests.yml#L45-L45.github/workflows/docker-tests.yml#L65-L65.github/workflows/docs_build.yml#L19-L19.github/workflows/docs_deploy.yml#L31-L33.github/workflows/lint.yml#L15-L15.github/workflows/lint.yml#L40-L40.github/workflows/lint.yml#L49-L51.github/workflows/lint.yml#L63-L65.github/workflows/lint.yml#L78-L80.github/workflows/proto.yml#L14-L14.github/workflows/release-apps.yml#L27-L27.github/workflows/release-apps.yml#L78-L78.github/workflows/release-github.yml#L35-L37🤖 Prompt for AI Agents
Source: Linters/SAST tools