Skip to content

chore(deps)!: update GitHub Actions (major) - #70

Open
williaby wants to merge 1 commit into
mainfrom
renovate/major-github-actions
Open

chore(deps)!: update GitHub Actions (major)#70
williaby wants to merge 1 commit into
mainfrom
renovate/major-github-actions

Conversation

@williaby

@williaby williaby commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Why

Scheduled patch update, bug fixes and security patches with no API changes.

Changes

This PR contains the following updates:

Package Type Update Change OpenSSF
actions/checkout action major v6.0.2v7.0.1 OpenSSF Scorecard
actions/setup-python action major v6.2.0v7.0.0 OpenSSF Scorecard
astral-sh/setup-uv action major v8.1.0v9.0.0 OpenSSF Scorecard

Impact

  • ✅ Patch update: bug fixes and security patches only
  • ✅ No breaking changes

Acceptance Criteria

  • All CI checks pass

Testing

  • CI gates pass (tests, lint, type checking, security scan)

Notes


Release Notes

actions/checkout (actions/checkout)

v7.0.1

Compare Source

v7.0.0

Compare Source

  • Block checking out fork PR for pull_request_target and workflow_run by @​aiqiaoy in #​2454
  • Various dependency updates

v7

Compare Source

v6.1.0

Compare Source

What's Changed

https://github.blog/changelog/2026-06-18-safer-pull_request_target-defaults-for-github-actions-checkout/ for more details about this breaking change

Full Changelog: actions/checkout@v6.0.3...v6.1.0

v6.0.3

Compare Source

actions/setup-python (actions/setup-python)

v7.0.0

Compare Source

What's Changed
Enhancements
Bug Fix
Dependency Upgrade
New Contributors

Full Changelog: actions/setup-python@v6...v7.0.0

v7

Compare Source

v6.3.0

Compare Source

What's Changed
Enhancement
Dependency update
Documentation
New Contributors

Full Changelog: actions/setup-python@v6.2.0...v6.3.0

astral-sh/setup-uv (astral-sh/setup-uv)

v9.0.0: 🌈 Change prune-cache default to false

Compare Source

Changes

This release disables the default cache cache pruning to ease the load on the PyPi infrastructure.
Since users might experience more GitHub Actions cache usage which might result in higher costs this is marked as a breaking change. To read more on why we did this (now) you can read the detailed analysis and reasoning in #​967

Besides this big breaking change we also have a small bugfix while building caches for linux distributions that behave a big different than the "big ones" and a speed up in version resolution by only reading the version manifest until a matching version is found saving runtime and network bandwith.

🚨 Breaking changes
🐛 Bug fixes
  • fix: fall back to distribution ID when os-release has no version field @​cxzhong (#​961)
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v8.3.2: 🌈 update known checksums for 0.11.28

Compare Source

Changes

Just a maintenance release

🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v8.3.1: 🌈 update known checksums for 0.11.27

Compare Source

Changes

Just a maintenance release

🧰 Maintenance
📚 Documentation

v8.3.0: 🌈 Support uv.lock as a version-file source

Compare Source

Changes

Thanks to @​somaz94 you can now use the pinned version of uv itself in uv.lock. It gets picked up automatically.
If you have pinned another version of uv in your uv.lock you can use the inputs version or version-source to override this.

🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v8.2.0: 🌈 New inputs quiet and download-from-astral-mirror

Compare Source

Changes

This release brings two new inputs and a few bug fixes.

New inputs

Lets talk about the new inputs first.

quiet

Pretty simple. It turns of all info loggings. Useful if you use this in a composite action and are not interested in all the details.
In the upcoming releases we will add log groups to fully implement support for "less noise"

[!NOTE]
Warnings and errors are always logged.

download-from-astral-mirror

In some cases you may want to directly use the fallback of checking for available versions and downloading releases from GitHub instead of using the astral.sh mirror. Setting download-from-astral-mirror: false allows you to do that.

Bugfixes

When using the astral.sh mirror to query available versions and download releases (done by default) we now stop sending the GitHub token in the header. The mirror never looked at it but we shouldn't be handing out that data even if it is just a short lived token.
All other bugfixes try to limit the impact of failed GitHub queries due to retries and other faults.

We couldn't pinpoint all rootcauses yet but added more logging for error cases to track them down.

🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • "after 10pm every weekday,before 5am every weekday,every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

Copilot AI review requested due to automatic review settings June 20, 2026 20:05
@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

Next included review available in 59 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: 9dc756e6-74d8-4aec-a84a-8a9c1f85b8b6

📥 Commits

Reviewing files that changed from the base of the PR and between ac864dd and 85fe62a.

📒 Files selected for processing (4)
  • .github/workflows/codeql.yml
  • .github/workflows/fips-compatibility.yml
  • .github/workflows/pr-validation.yml
  • .github/workflows/slsa-provenance.yml

Walkthrough

Nine GitHub Actions workflows update actions/checkout from v6.0.2 to v7.0.1. Five workflows also update actions/setup-python from v6.2.0 to v7.0.0. Existing workflow configuration and logic remain unchanged.

Changes

Workflow action updates

Layer / File(s) Summary
Checkout action updates
.github/workflows/*.yml
Checkout action pins are updated to v7.0.1 across the CI, validation, release, provenance, and analysis workflows.
Python setup action updates
.github/workflows/codeql.yml, .github/workflows/pr-validation.yml, .github/workflows/slsa-provenance.yml, .github/workflows/sonarcloud.yml, .github/workflows/validate-cruft.yml
Python setup action pins are updated to v7.0.0; surrounding workflow steps and configuration are unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related issues

  • ByronWilliamsCPA/.claude#60 — Tracks similar GitHub Actions dependency updates, including checkout and setup-python.

Suggested labels: ci

Suggested reviewers: byronwilliamscpa

Poem

🐇 Pins hop forward, neat and bright,
Checkout runs with newer might.
Python follows down the lane,
Workflows keep their former train.
No steps changed—just versions gleam!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly reflects the main change: a major GitHub Actions dependency update with breaking-change intent.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/major-github-actions

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Jun 20, 2026

Copy link
Copy Markdown

⚠️ Deprecation Warning: The deny-licenses option is deprecated for possible removal in the next major release. For more information, see issue 997.

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
actions/actions/checkout 3d3c42e5aac5ba805825da76410c181273ba90b1 🟢 7
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1024 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts🟢 10no binaries found in the repo
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Packaging⚠️ -1packaging workflow not detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Pinned-Dependencies🟢 3dependency not pinned by hash detected -- score normalized to 3
Security-Policy🟢 9security policy file detected
SAST🟢 10SAST tool is run on all commits
Branch-Protection🟢 6branch protection is not maximal on development and all release branches
actions/actions/setup-python 5fda3b95a4ea91299a34e894583c3862153e4b97 🟢 6.6
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1021 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts🟢 10no binaries found in the repo
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies🟢 7dependency not pinned by hash detected -- score normalized to 7
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Security-Policy🟢 9security policy file detected
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST🟢 9SAST tool is not run on all commits -- score normalized to 9
actions/astral-sh/setup-uv c771a70e6277c0a99b617c7a806ffedaca235ff9 UnknownUnknown
actions/actions/checkout 3d3c42e5aac5ba805825da76410c181273ba90b1 🟢 7
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1024 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts🟢 10no binaries found in the repo
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Packaging⚠️ -1packaging workflow not detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Pinned-Dependencies🟢 3dependency not pinned by hash detected -- score normalized to 3
Security-Policy🟢 9security policy file detected
SAST🟢 10SAST tool is run on all commits
Branch-Protection🟢 6branch protection is not maximal on development and all release branches
actions/actions/setup-python 5fda3b95a4ea91299a34e894583c3862153e4b97 🟢 6.6
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1021 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts🟢 10no binaries found in the repo
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies🟢 7dependency not pinned by hash detected -- score normalized to 7
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Security-Policy🟢 9security policy file detected
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST🟢 9SAST tool is not run on all commits -- score normalized to 9

Scanned Files

  • .github/workflows/pr-validation.yml
  • .github/workflows/validate-cruft.yml

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the pinned actions/checkout GitHub Action across this repository’s CI/security workflows to the v7 release series (via a new commit SHA), keeping workflows aligned on the same checkout implementation.

Changes:

  • Bumped actions/checkout from v6.0.2 to v7 (new pinned SHA) in multiple workflows.
  • Kept existing checkout configuration (e.g., fetch-depth, persist-credentials) unchanged where present.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
.github/workflows/validate-cruft.yml Updates checkout action pin to v7 for cruft validation workflow.
.github/workflows/sonarcloud.yml Updates checkout action pin to v7 for SonarCloud analysis workflow.
.github/workflows/slsa-provenance.yml Updates checkout action pin to v7 for SLSA provenance build job.
.github/workflows/release-sign.yml Updates checkout action pin to v7 for release artifact signing workflow.
.github/workflows/pr-validation.yml Updates checkout action pin to v7 for PR validation jobs.
.github/workflows/fips-compatibility.yml Updates checkout action pin to v7 for FIPS compliance checks.
.github/workflows/dependency-review.yml Updates checkout action pin to v7 for dependency review workflow.
.github/workflows/codeql.yml Updates checkout action pin to v7 for CodeQL scanning workflow.
.github/workflows/cifuzzy.yml Updates checkout action pin to v7 for continuous fuzzing workflow.

Comment on lines 87 to 89
- name: Checkout repository
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7
with:
@williaby
williaby force-pushed the renovate/major-github-actions branch from dbfbcdb to 46ef537 Compare June 29, 2026 17:53
@coderabbitai coderabbitai Bot added the ci label Jun 29, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/cifuzzy.yml:
- Around line 50-51: In the Checkout repository step, the default GitHub token
is still being persisted in the local git config for the rest of the job. Update
the actions/checkout usage in cifuzzy.yml to disable credential persistence by
setting persist-credentials to false, matching the pattern already used in the
other upgraded workflows, and keep the change scoped to the Checkout repository
step.

In @.github/workflows/pr-validation.yml:
- Around line 58-59: The workflow’s Checkout repository step is still persisting
the GitHub token in local git config because actions/checkout defaults to
persist-credentials true. Update both checkout steps in the workflow to
explicitly disable credential persistence by setting persist-credentials to
false on the checkout action, keeping the change tied to the existing Checkout
repository step and actions/checkout usage.

In @.github/workflows/release-sign.yml:
- Around line 24-25: Disable persisted checkout credentials in the signing
workflow by updating the Checkout step in release-sign.yml so actions/checkout
does not write the repo token into .git/config; keep GH_TOKEN for gh separately
and configure the checkout action to avoid persisting credentials in the signing
job.

In @.github/workflows/slsa-provenance.yml:
- Around line 63-65: The checkout step in the SLSA provenance workflow should
stop persisting Git credentials. Update the existing actions/checkout usage in
the workflow job to include persist-credentials set to false while keeping
fetch-depth at 0, since there is no later authenticated git usage in this job.

In @.github/workflows/validate-cruft.yml:
- Around line 44-45: The checkout step in validate-cruft.yml still uses the
default credential persistence, which should be disabled to match the other
updated workflows. Update the actions/checkout usage in the Checkout repository
step to set persist-credentials to false so the job token is not left in local
Git config.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 90bb3408-5f99-4d83-bd93-a2701a4bb40e

📥 Commits

Reviewing files that changed from the base of the PR and between d992f0e and 46ef537.

📒 Files selected for processing (9)
  • .github/workflows/cifuzzy.yml
  • .github/workflows/codeql.yml
  • .github/workflows/dependency-review.yml
  • .github/workflows/fips-compatibility.yml
  • .github/workflows/pr-validation.yml
  • .github/workflows/release-sign.yml
  • .github/workflows/slsa-provenance.yml
  • .github/workflows/sonarcloud.yml
  • .github/workflows/validate-cruft.yml

Comment thread .github/workflows/cifuzzy.yml Outdated
Comment on lines +50 to +51
- name: Checkout repository
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

Copy link
Copy Markdown

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

Disable checkout credential persistence.

Line 51 leaves the default GitHub token in the local git config for the rest of the job. Add persist-credentials: false here, as you already do in the other upgraded workflows.

Suggested fix
       - name: Checkout repository
         uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          persist-credentials: false
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Checkout repository
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
- name: Checkout repository
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
persist-credentials: false
🧰 Tools
🪛 zizmor (1.26.1)

[warning] 50-51: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/cifuzzy.yml around lines 50 - 51, In the Checkout
repository step, the default GitHub token is still being persisted in the local
git config for the rest of the job. Update the actions/checkout usage in
cifuzzy.yml to disable credential persistence by setting persist-credentials to
false, matching the pattern already used in the other upgraded workflows, and
keep the change scoped to the Checkout repository step.

Sources: Path instructions, Linters/SAST tools

Comment thread .github/workflows/pr-validation.yml Outdated
Comment on lines +58 to +59
- name: Checkout repository
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail
file=".github/workflows/pr-validation.yml"

echo "Checkout blocks in $file:"
sed -n '48,120p' "$file"

echo
echo "Verify whether these jobs need authenticated git after checkout:"
rg -n -C2 'uses:\s*actions/checkout@|persist-credentials|git\s+(push|fetch|pull|submodule)|gh\s' "$file"

Repository: ByronWilliamsCPA/audio-processor

Length of output: 3327


🏁 Script executed:

#!/bin/bash
set -euo pipefail
file=".github/workflows/pr-validation.yml"

echo "Workflow header and permissions:"
sed -n '1,80p' "$file"

echo
echo "All git/gh/auth-related references in the workflow:"
rg -n -C2 '\b(git|gh|checkout|token|permissions:|persist-credentials)\b' "$file"

echo
echo "Job names and steps summary:"
python3 - <<'PY'
from pathlib import Path
import re
text = Path(".github/workflows/pr-validation.yml").read_text()
for m in re.finditer(r'^\s{2}([A-Za-z0-9_-]+):\n(?:.*\n)*?(?=^\s{2}[A-Za-z0-9_-]+:|\Z)', text, re.M):
    job = m.group(1)
    block = m.group(0)
    steps = re.findall(r'^\s{6}- name: (.+)$', block, re.M)
    print(f"{job}:")
    for s in steps:
        print(f"  - {s}")
PY

Repository: ByronWilliamsCPA/audio-processor

Length of output: 3740


Disable checkout credential persistence in both jobs.
Both actions/checkout steps leave the workflow token in local git config via the default persist-credentials: true, which is unnecessary here.

Suggested change
       - name: Checkout repository
         uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          persist-credentials: false
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Checkout repository
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
- name: Checkout repository
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
persist-credentials: false
🧰 Tools
🪛 zizmor (1.26.1)

[warning] 58-59: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/pr-validation.yml around lines 58 - 59, The workflow’s
Checkout repository step is still persisting the GitHub token in local git
config because actions/checkout defaults to persist-credentials true. Update
both checkout steps in the workflow to explicitly disable credential persistence
by setting persist-credentials to false on the checkout action, keeping the
change tied to the existing Checkout repository step and actions/checkout usage.

Sources: Path instructions, Linters/SAST tools

Comment thread .github/workflows/release-sign.yml Outdated
Comment on lines +24 to +25
- name: Checkout
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail
file=".github/workflows/release-sign.yml"

sed -n '12,40p' "$file"
echo
rg -n -C2 'uses:\s*actions/checkout@|persist-credentials|GH_TOKEN|gh\s' "$file"

Repository: ByronWilliamsCPA/audio-processor

Length of output: 2664


🏁 Script executed:

#!/bin/bash
set -euo pipefail

file=".github/workflows/release-sign.yml"

ast-grep outline "$file" --view expanded || true
echo "-----"
sed -n '1,220p' "$file"
echo "-----"
rg -n 'git |git\W|gh release|checkout|persist-credentials|remote|push|fetch|upload|download|cosign|GH_TOKEN' "$file"

Repository: ByronWilliamsCPA/audio-processor

Length of output: 4168


Disable persisted checkout credentials in the signing job.
gh already gets GH_TOKEN explicitly, so actions/checkout should not leave a repo token in .git/config for this workflow.

🧰 Tools
🪛 zizmor (1.26.1)

[warning] 24-25: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/release-sign.yml around lines 24 - 25, Disable persisted
checkout credentials in the signing workflow by updating the Checkout step in
release-sign.yml so actions/checkout does not write the repo token into
.git/config; keep GH_TOKEN for gh separately and configure the checkout action
to avoid persisting credentials in the signing job.

Sources: Path instructions, Linters/SAST tools

Comment thread .github/workflows/slsa-provenance.yml Outdated
Comment on lines 63 to 65
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
fetch-depth: 0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail
file=".github/workflows/slsa-provenance.yml"

sed -n '42,90p' "$file"
echo
rg -n -C2 'uses:\s*actions/checkout@|persist-credentials|git\s+(push|fetch|pull|submodule)|gh\s' "$file"

Repository: ByronWilliamsCPA/audio-processor

Length of output: 2112


🏁 Script executed:

#!/bin/bash
set -euo pipefail
file=".github/workflows/slsa-provenance.yml"

echo "== top =="
sed -n '1,120p' "$file"

echo
echo "== checkout / git / gh usage =="
rg -n -C3 'actions/checkout|persist-credentials|git\s+(push|fetch|pull|submodule|config|remote)|gh\s|github-token|token:' "$file"

Repository: ByronWilliamsCPA/audio-processor

Length of output: 4839


Disable persisted checkout credentials here. fetch-depth: 0 still works with persist-credentials: false, and this job doesn’t show any authenticated git use after checkout.

🧰 Tools
🪛 zizmor (1.26.1)

[warning] 62-65: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/slsa-provenance.yml around lines 63 - 65, The checkout
step in the SLSA provenance workflow should stop persisting Git credentials.
Update the existing actions/checkout usage in the workflow job to include
persist-credentials set to false while keeping fetch-depth at 0, since there is
no later authenticated git usage in this job.

Source: Path instructions

Comment thread .github/workflows/validate-cruft.yml Outdated
Comment on lines +44 to +45
- name: Checkout repository
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

Copy link
Copy Markdown

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

Disable checkout credential persistence here as well.

Line 45 keeps checkout's default credential persistence enabled, which is inconsistent with the safer pattern already used in the other bumped workflows. Add persist-credentials: false to avoid leaving the job token in local Git config.

Suggested fix
       - name: Checkout repository
         uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          persist-credentials: false
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Checkout repository
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
- name: Checkout repository
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
persist-credentials: false
🧰 Tools
🪛 zizmor (1.26.1)

[warning] 44-45: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/validate-cruft.yml around lines 44 - 45, The checkout step
in validate-cruft.yml still uses the default credential persistence, which
should be disabled to match the other updated workflows. Update the
actions/checkout usage in the Checkout repository step to set
persist-credentials to false so the job token is not left in local Git config.

Sources: Path instructions, Linters/SAST tools

@williaby
williaby force-pushed the renovate/major-github-actions branch 2 times, most recently from ac864dd to 9ac8b89 Compare July 24, 2026 17:06
@williaby williaby changed the title chore(deps)!: update GitHub Actions to v7 chore(deps)!: update GitHub Actions (major) Jul 24, 2026
@sonarqubecloud

Copy link
Copy Markdown

@williaby
williaby force-pushed the renovate/major-github-actions branch from 9ac8b89 to 85fe62a Compare September 3, 2026 16:39
@sonarqubecloud

sonarqubecloud Bot commented Sep 3, 2026

Copy link
Copy Markdown

@williaby
williaby added this pull request to the merge queue Sep 3, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants