[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
actions/download-artifact	action	digest	3e5f45b → 9000827
actions/upload-artifact	action	digest	043fb46 → cf430e0
codecov/codecov-action	action	minor	v7.0.0 → v7.1.1
conforma/github-workflows	workflow	pinDigest	→ 9e47833
github/codeql-action	action	minor	v4.32.6 → v4.39.1
google-github-actions/run-gemini-cli	action	pinDigest	→ f77273f
ossf/scorecard-action	action	minor	v2.4.4 → v2.5.0
step-security/harden-runner	action	minor	v2.15.1 → v2.22.2	v2.22.3

---

Release Notes

codecov/codecov-action

v7.1.1

Compare Source

What's Changed

• chore(release): 7.1.1 by @​thomasrockhu-codecov in #​1973

Full Changelog: codecov/codecov-action@v7.1.0...v7.1.1

v7.1.0

Compare Source

What's Changed

• chore(release): 7.1.0 by @​thomasrockhu-codecov in #​1971

Full Changelog: codecov/codecov-action@v7.0.0...v7.1.0

github/codeql-action

v4.39.1

Compare Source

• Update default CodeQL bundle version to 2.27.3. #​4256

v4.39.0

Compare Source

• Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #​4205
• The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #​4148
• Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #​4206
• The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #​4198

v4.38.3

Compare Source

• Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #​4188
• Update default CodeQL bundle version to 2.27.2. #​4203
• Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #​4184

v4.38.2

Compare Source

• Update default CodeQL bundle version to 2.27.1. #​4160

v4.38.1

Compare Source

• The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #​4146

v4.38.0

Compare Source

• On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #​4124
• The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #​4072
• Update default CodeQL bundle version to 2.27.0. #​4129

v4.37.9

Compare Source

• Update default CodeQL bundle version to 2.26.4. #​4106

v4.37.8

Compare Source

No user facing changes.

v4.37.7

Compare Source

• Update default CodeQL bundle version to 2.26.3. #​4085

v4.37.6

Compare Source

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #​4070

v4.37.5

Compare Source

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #​4061

v4.37.4

Compare Source

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #​4037
• Update default CodeQL bundle version to 2.26.2. #​4051

v4.37.3

Compare Source

No user facing changes.

v4.37.2

Compare Source

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #​4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #​4007

v4.37.1

Compare Source

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #​3956
• Update default CodeQL bundle version to 2.26.1. #​4019

v4.37.0

Compare Source

• Update default CodeQL bundle version to 2.26.0. #​3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #​3973

v4.36.3

Compare Source

No user facing changes.

v4.36.2

Compare Source

• Cache CodeQL CLI version information across Actions steps. #​3943
• Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #​3937
• Update default CodeQL bundle version to 2.25.6. #​3948

v4.36.1

Compare Source

No user facing changes.

v4.36.0

Compare Source

• Breaking change: Bump the minimum required CodeQL bundle version to 2.19.4. #​3894
• Add support for SHA-256 Git object IDs. #​3893
• Update default CodeQL bundle version to 2.25.5. #​3926

v4.35.5

Compare Source

• We have improved how the JavaScript bundles for the CodeQL Action are generated to avoid duplication across bundles and reduce the size of the repository by around 70%. This should have no effect on the runtime behaviour of the CodeQL Action. #​3899
• For performance and accuracy reasons, improved incremental analysis will now only be enabled on a pull request when diff-informed analysis is also enabled for that run. If diff-informed analysis is unavailable (for example, because the PR diff ranges could not be computed), the action will fall back to a full analysis. #​3791
• If multiple inputs are provided for the GitHub-internal analysis-kinds input, only code-scanning will be enabled. The analysis-kinds input is experimental, for GitHub-internal use only, and may change without notice at any time. #​3892
• Added an experimental change which, when running a Code Scanning analysis for a PR with improved incremental analysis enabled, prefers CodeQL CLI versions that have a cached overlay-base database for the configured languages. This speeds up analysis for a repository when there is not yet a cached overlay-base database for the latest CLI version. We expect to roll this change out to everyone in May. #​3880

v4.35.4

Compare Source

• Update default CodeQL bundle version to 2.25.4. #​3881

v4.35.3

Compare Source

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.19.3 and earlier. These versions of CodeQL were discontinued on 9 April 2026 alongside GitHub Enterprise Server 3.15, and will be unsupported by the next minor release of the CodeQL Action. #​3837
• Configurations for private registries that use Cloudsmith or GCP OIDC are now accepted. #​3850
• Best-effort connection tests for private registries now use GET requests instead of HEAD for better compatibility with various registry implementations. For NuGet feeds, the test is now always performed against the service index. #​3853
• Fixed a bug where two diagnostics produced within the same millisecond could overwrite each other on disk, causing one of them to be lost. #​3852
• Update default CodeQL bundle version to 2.25.3. #​3865

v4.35.2

Compare Source

• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable is deprecated and will be removed in May 2026. If you are affected by this, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #​3795
• The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #​3789
• Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. #​3794
• Fixed a bug in the validation of OIDC configurations for private registries that was added in CodeQL Action 4.33.0 / 3.33.0. #​3807
• Update default CodeQL bundle version to 2.25.2. #​3823

v4.35.1

Compare Source

• Fix incorrect minimum required Git version for improved incremental analysis: it should have been 2.36.0, not 2.11.0. #​3781

v4.35.0

Compare Source

• Reduced the minimum Git version required for improved incremental analysis from 2.38.0 to 2.11.0. #​3767
• Update default CodeQL bundle version to 2.25.1. #​3773

v4.34.1

Compare Source

• Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #​3762

v4.34.0

Compare Source

• Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #​3569
• We are rolling out improved incremental analysis to C/C++ analyses that use build mode none. We expect this rollout to be complete by the end of April 2026. #​3584
• Update default CodeQL bundle version to 2.25.0. #​3585

v4.33.0

Compare Source

• Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #​3562

  To opt out of this change:

  • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • User-owned repositories using advanced setup: Set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.

• Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #​3557

• The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as github-codeql-disable-overlay that was previously only available on GitHub.com. #​3559

• Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #​3563

• Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #​3564

• A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #​3570

ossf/scorecard-action

v2.5.0

Compare Source

What's Changed

This release moves the action to Scorecard v5.6.0, the first Scorecard release since its hosted
services moved to new infrastructure.

For changes to checks and results, and what the infrastructure move means for you, see the
Scorecard v5.6.0 release notes.

• The action's container image is built with Go 1.27.2 on a refreshed distroless base. by
  @​justaugustus in #​1716
• The installer (cmd/installer) now creates .github/workflows/scorecard.yml, and still
  recognizes existing scorecards.yml and scorecards-analysis.yml workflows. by @​justaugustus in #​1716
• The Scorecard version in results now always matches the Scorecard release the action is built
  with. by @​justaugustus in #​1718
• The action no longer prints the GitHub token variable while validating its options. by
  @​arpitjain099 in #​1709
• results_format accepts intoto, which wraps the JSON results in an in-toto attestation
  statement. by @​puerco in #​1702

Other

• Add a daily canary against Scorecard main by @​justaugustus in #​1711
• Bump Scorecard to the v5.6.0 candidate and fix the canary toolchain by @​justaugustus in #​1714
• Run Scorecard on every merge, add a zizmor presubmit, analyze workflows with CodeQL, and update
  RELEASE.md by @​justaugustus in #​1716
• Bump Scorecard to v5.6.0 by @​justaugustus in #​1719

New Contributors

• @​arpitjain099 made their first contribution in #​1709
• @​puerco made their first contribution in #​1702

Full Changelog: ossf/scorecard-action@v2.4.4...v2.5.0

step-security/harden-runner

v2.22.2

Compare Source

What's Changed

• Fixed inbound (ingress) network traffic being incorrectly classified as outbound (egress) traffic on macOS
• Fixed implicit endpoints intended for self-hosted runners being applied to custom VM environments on Linux (enterprise tier)
• Improved network and DNS tracing, enforcement logic, and process information correlation on Linux (enterprise tier)

Full Changelog: step-security/harden-runner@v2.22.1...v2.22.2

v2.22.1

Compare Source

What's Changed

• Fixed security rules not initializing on GHES self-hosted runners
• Fixed GHES connectivity in block mode by implicitly allowing the GHES hostname

Full Changelog: step-security/harden-runner@v2.22.0...v2.22.1

v2.22.0

Compare Source

What's Changed

• Linux ARM64 support for community tier
• GHES support for self-hosted VMs (enterprise tier)
• MacOS and Windows runner deny list support for block policy (enterprise tier).

Full Changelog: step-security/harden-runner@v2.21.1...v2.22.0

v2.21.1

Compare Source

What's Changed

• Improved performance of the disable-sudo feature.
• Fixed an issue in the Community tier where new endpoints required by the GitHub Actions runner were not being implicitly allowed in block mode.
• Fixed the Harden-Runner post step failing on Linux distributions that do not have a merged /usr filesystem layout (for example Debian 11), where /usr/bin/echo does not exist. This mainly affected self-hosted runners.
• Documentation updates: clarified which features are in the Community (free) vs Enterprise tier.

Full Changelog: step-security/harden-runner@v2.21.0...v2.21.1

v2.21.0

Compare Source

What's Changed

• Support for denied endpoints in block mode. This is included in the enterprise tier. Customers can deny outbound calls, for example, to public package registries.
• Improved Support for AWS CodeBuild GitHub Actions Runners.
• Bug fixes.

Full Changelog: step-security/harden-runner@v2.20.1...v2.21.0

v2.20.1

Compare Source

What's Changed

• AWS CodeBuild-hosted runner support
• Implicitly allow single-labeled (internal) domains in block-mode

Full Changelog: step-security/harden-runner@v2.20.0...v2.20.1

v2.20.0

Compare Source

What's Changed

• Support for block policy for MacOS and Windows GitHub-hosted runners
• Support for Bitrise MacOS GitHub Actions runners
• HTTPS monitoring support for Bun for Linux runners (enterprise tier)

Full Changelog: step-security/harden-runner@v2.19.4...v2.20.0

v2.19.4

Compare Source

What's Changed

• Improvements for HTTPS Monitoring for the Enterprise tier of Harden Runner

Full Changelog: step-security/harden-runner@v2.19.3...v2.19.4

v2.19.3

Compare Source

What's Changed

• Default to audit mode when api-key missing with use-policy-store by @​varunsh-coder in #​665

Full Changelog: step-security/harden-runner@v2.19.2...v2.19.3

v2.19.2

Compare Source

What's Changed

• Update the Harden Runner agent for enterprise tier to use go 1.26 and fix minor bugs.

Full Changelog: step-security/harden-runner@v2.19.1...v2.19.2

v2.19.1

Compare Source

What's Changed

• fix: detect ubuntu-slim runners early and bail out by @​devantler in #​657

What the fix changes

• Harden-Runner will detect ubuntu-slim runners and exit cleanly with an informational log message, instead of post harden runner step failing on chown: invalid user: 'undefined'.

What the fix does not do

• Jobs running on ubuntu-slim will not be monitored by Harden-Runner. The agent relies on kernel-level features (that require elevated capabilities).
• Per GitHub's docs on single-CPU runners: "The container for ubuntu-slim runners runs in unprivileged mode. This means that some operations requiring elevated privileges such as mounting file systems, using Docker-in-Docker, or accessing low-level kernel features are not supported." Those low-level kernel features are what the agent needs, so monitoring inside the unprivileged container is not feasible today.

For StepSecurity enterprise customers
If your security posture requires that workflows are always monitored, you can block the use of ubuntu-slim via workflow run policies see the Runner Label Policy docs. This lets you enforce that jobs only run on monitored runner types.

New Contributors

• @​devantler made their first contribution in #​657

Full Changelog: step-security/harden-runner@v2.19.0...v2.19.1

v2.19.0

Compare Source

What's Changed

New Runner Support

Harden-Runner now supports Depot, Blacksmith, Namespace, and WarpBuild runners with the same egress monitoring, runtime monitoring, and policy enforcement available on GitHub-hosted runners.

Automated Incident Response for Supply Chain Attacks

• Global block list: Outbound connections to known malicious domains and IPs are now blocked even in audit mode.
• System-defined detection rules: Harden-Runner will trigger lockdown mode when a high risk event is detected during an active supply chain attack (for example, a process reading the memory of the runner worker process, a common technique for stealing GitHub Actions secrets).

Bug Fixes

Windows and macOS: stability and reliability fixes

Full Changelog: step-security/harden-runner@v2.18.0...v2.19.0

v2.18.0

Compare Source

What's Changed

Global Block List: During supply chain incidents like the recent axios and trivy compromises, StepSecurity will add known malicious domains and IP addresses (IOCs) to a global block list. These will be automatically blocked, even in audit mode, providing immediate protection without requiring any workflow changes.

Deploy on Self-Hosted VM: Added deploy-on-self-hosted-vm input that allows the Harden Runner agent to be installed directly on ephemeral self-hosted Linux runner VMs at workflow runtime. This is intended as an alternative when baking the agent into the VM image is not possible.

Full Changelog: step-security/harden-runner@v2.17.0...v2.18.0

v2.17.0

Compare Source

What's Changed

Policy Store Support

Added use-policy-store and api-key inputs to fetch security policies directly from the StepSecurity Policy Store. Policies can be defined and attached at the workflow, repo, org, or cluster (ARC) level, with the most granular policy taking precedence. This is the preferred method over the existing policy input which requires id-token: write permission. If no policy is found in the store, the action defaults to audit mode.

Full Changelog: step-security/harden-runner@v2.16.1...v2.17.0

v2.16.1

Compare Source

What's Changed

Enterprise tier: Added support for direct IP addresses in the allow list
Community tier: Migrated Harden Runner telemetry to a new endpoint

Full Changelog: step-security/harden-runner@v2.16.0...v2.16.1

v2.16.0

Compare Source

What's Changed

• Updated action.yml to use node24
• Security fix: Fixed a medium severity vulnerability where the egress block policy could be bypassed via DNS over HTTPS (DoH) by proxying DNS queries through a permitted resolver, allowing data exfiltration even with a restrictive allowed-endpoints list. This issue only affects the Community Tier; the Enterprise Tier is not affected. See GHSA-46g3-37rh-v698 for details.
• Security fix: Fixed a medium severity vulnerability where the egress block policy could be bypassed via DNS queries over TCP to external resolvers, allowing outbound network communication that evades configured network restrictions. This issue only affects the Community Tier; the Enterprise Tier is not affected. See GHSA-g699-3x6g-wm3g for details.

Full Changelog: step-security/harden-runner@v2.15.1...v2.16.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[fullsend-ai-review]

Review

Findings

High

• [protected-path] .github/workflows/ — This PR modifies 6 files under protected paths (.github/workflows/auto-merge.yaml, .github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml). The PR has no linked issue providing authorization context for modifying governance or infrastructure files. Human approval is required for all protected-path changes.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W119 -->

Review

Findings

High

• [protected-path] .github/workflows/auto-merge.yaml — All 6 changed files are under the .github/ protected path (auto-merge.yaml, codeql.yml, pre-merge-ci.yaml, push-bundles.yaml, release.yaml, scorecards.yml). This PR has no linked issue providing justification for modifying governance or infrastructure files. Human approval is always required for protected-path changes.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (2)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W119 -->

Review

Findings

High

• [protected-path] .github/workflows/ — This PR modifies 6 files under the .github/ protected path: auto-merge.yaml, codeql.yml, pre-merge-ci.yaml, push-bundles.yaml, release.yaml, scorecards.yml. No linked issue provides justification for modifying governance or infrastructure files. Human approval is required for protected-path changes.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (3)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W119 -->

Review

Findings

High

• [protected-path] .github/workflows/ — All six changed files are under the .github/ protected path. This Renovate-generated PR updates GitHub Actions dependency digests and versions (step-security/harden-runner v2.15.1 → v2.22.2, github/codeql-action v4.32.6 → v4.39.0, codecov/codecov-action v7.0.0 → v7.1.1, ossf/scorecard-action v2.4.4 → v2.5.0, conforma/github-workflows pinned to SHA, google-github-actions/run-gemini-cli pinned to SHA, actions/upload-artifact and actions/download-artifact updated) but has no linked issue providing explicit authorization for modifying governance/infrastructure files. Affected files: auto-merge.yaml, codeql.yml, pre-merge-ci.yaml, push-bundles.yaml, release.yaml, scorecards.yml. Human approval is always required for protected-path changes regardless of context.

Low

• [sub-agent-failure] N/A — The challenger sub-agent returned invalid adjudication accounting (used 'downgraded' action without severity change on info-level findings). Pre-challenger finding set used.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (4)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W119 -->

Review

Findings

High

• [protected-path] .github/workflows/ — This PR modifies 6 files under the protected .github/ path: auto-merge.yaml, codeql.yml, pre-merge-ci.yaml, push-bundles.yaml, release.yaml, and scorecards.yml. The PR has no linked issue justifying changes to governance/infrastructure files. Human approval is required for all protected-path changes.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (5)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W119 -->

Review

Findings

High

• [protected-path] .github/workflows/auto-merge.yaml — This PR modifies 6 files under protected paths (.github/workflows/): auto-merge.yaml, codeql.yml, pre-merge-ci.yaml, push-bundles.yaml, release.yaml, scorecards.yml. The PR has no linked issue providing justification for modifying governance or infrastructure files. Human approval is required for protected-path changes.

---

Labels: Renovate PR updating GitHub Actions version pins across workflow files.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (6)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W119 -->

Review

Findings

High

• [protected-path] .github/workflows/* — All 6 changed files are under the .github/ protected path prefix. This Renovate bot PR updates GitHub Actions digests and versions but has no linked issue providing justification for modifying governance and infrastructure files. Protected files: auto-merge.yaml, codeql.yml, pre-merge-ci.yaml, push-bundles.yaml, release.yaml, scorecards.yml. Human approval is always required for protected-path changes.

---

Labels: PR modifies GitHub Actions workflows and is authored by Renovate bot

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (7)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W119 -->

Review

Findings

High

• [protected-path] .github/workflows/ — This PR modifies six files under the protected .github/workflows/ path (auto-merge.yaml, codeql.yml, pre-merge-ci.yaml, push-bundles.yaml, release.yaml, scorecards.yml) and has no linked issue authorizing changes to governance/CI infrastructure files. Standing authorization via renovate.json (which extends conforma/.github//config/renovate/renovate.json) covers the Renovate workflow pattern, and the body details each digest/version bump — but the governance rule for protected paths requires an explicit human authorization reference before merge. Human approval is required.
  Remediation: Link the PR to an issue (or policy entry) authorizing routine Renovate digest bumps under .github/workflows/, and have a human reviewer explicitly approve.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (8)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W119 -->

Review

Findings

High

• [protected-path] .github/workflows/ — This PR modifies six files under the protected .github/workflows/ path (auto-merge.yaml, codeql.yml, pre-merge-ci.yaml, push-bundles.yaml, release.yaml, scorecards.yml) and has no linked issue authorizing changes to governance / CI infrastructure files. Even though the description details the Renovate action-digest bumps, protected-path changes require an explicit human authorization reference. Human approval is required before merge.
  Remediation: Link the PR to an issue (or policy entry) authorizing routine Renovate digest bumps under .github/workflows/, and have a human reviewer explicitly approve.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (9)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

Review

Findings

Medium

• [protected-path] .github/workflows/ — This PR modifies protected governance paths: .github/workflows/auto-merge.yaml, .github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, and .github/workflows/scorecards.yml. Standing authorization exists for Renovate-generated GitHub Action pin updates via renovate.json (which extends conforma/.github//config/renovate/renovate.json), and the PR body explains each dependency update with release notes. Human approval is always required for protected-path changes, regardless of context.
  Remediation: Human reviewer confirms the pinned SHAs and version bumps are appropriate for this release branch and merges when CI passes.

Previous run (10)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

Review

Findings

Medium

• [protected-path] .github/workflows/ — All six changed files are under .github/workflows/, which is a protected path requiring human approval. The PR has no linked issue, but the Renovate-generated description explains each update individually (step-security/harden-runner v2.15.1→v2.22.0, github/codeql-action v4.32.6→v4.38.2, codecov/codecov-action v7.0.0→v7.1.1, conforma/github-workflows pinDigest, google-github-actions/run-gemini-cli pinDigest), and the repo's renovate.json provides standing authorization for Renovate to maintain pinned action references. Human approval is still required for all protected-path changes regardless of context — see the requires-manual-review label.
  Remediation: Human reviewer should confirm the pin targets are the intended upstream releases before merging.

Previous run (11)

Review

Findings

Medium

• [protected-path] .github/workflows/ — All 6 modified files are under .github/ (protected path). This is a Renovate PR bumping pinned SHA/version references of third-party GitHub Actions (step-security/harden-runner, github/codeql-action, codecov/codecov-action) and adding first-time pinDigest to conforma/github-workflows/.github/workflows/auto-merge.yaml and google-github-actions/run-gemini-cli. Repo-level renovate.json (extends github>conforma/.github//config/renovate/renovate.json) authorizes Renovate for this pattern. All new references remain pinned to full commit SHAs with version comments; permissions: and secrets: blocks are unchanged. Human approval is still required for any change under a protected path.

Info

• [provenance-warning] — Prior review context discarded: provenance validation failed (unverifiable-wrong-app). This review treats all findings as first-time assessments; severity anchoring was skipped for this run.

Previous run (12)

Looks good to me

Previous run (13)

Automated Renovate SHA-pin / minor-version bump for four GitHub Actions across six workflow files under .github/workflows/ (26 lines total). Correctness, security, and style/conventions review found no blocking issues; scope authorization is inferred from the mechanical nature of the change and the repo's Renovate configuration (renovate.json).

Because this PR modifies protected paths (.github/), human approval is required regardless of automated review.

Previous run (14)

Review

Findings

Medium

• [protected-path] .github/workflows/ — This PR modifies 6 files under .github/, which is a protected governance/infrastructure path. Affected files: .github/workflows/auto-merge.yaml, .github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml. The Renovate-generated PR body enumerates every dependency change and version delta, providing sufficient context for the update. Human approval is always required for protected-path changes, regardless of context.

Notes

All changes are mechanical: version+digest bumps of already-digest-pinned actions, plus new digest pinning of previously floating refs (conforma/github-workflows@main, google-github-actions/run-gemini-cli@v0, actions/upload-artifact@v6, actions/download-artifact@v7). Digest pinning of previously floating refs is a supply-chain hardening improvement. No permissions: or secrets: blocks are modified. No workflow triggers change.

Correctness, security, and style/conventions sub-agents each returned no findings on the diff itself.

Previous run (15)

Review

Renovate GitHub Actions dependency update: 6 workflow files under .github/workflows/, 25 additions / 25 deletions, all uses: line changes. Two patterns: (1) SHA-pin refreshes for already-pinned actions bumping through minor versions, and (2) new SHA pins for previously-floating references (@main, @v0, @v6, @v7). No permissions:, secrets:, workflow logic, or source code touched.

All files under .github/workflows/ are on the protected-path list, so approval is deferred to a human reviewer even though the change is a routine Renovate update authorized by the repository's renovate.json.

Findings

Info

• [protected-path] .github/workflows/ — All six changed files are under .github/workflows/, which is on the REVIEW_PROTECTED_PATHS list. Renovate-driven authorization is inferred from the repository's renovate.json (extending github>conforma/.github//config/renovate/renovate.json) and the mechanical nature of the change (dependency version + digest bumps only). Human approval is still required for protected-path changes; this finding is downgraded to info following reconciliation with the scope-authorization-implicit finding below, which cites the same authorization evidence.
• [permission-reduction] .github/workflows/auto-merge.yaml — Reusable-workflow reference pinned from conforma/github-workflows/.github/workflows/auto-merge.yaml@main to commit SHA 837d70f4c5dd1e709fc689c3a0f9a6f26029339a. Eliminates a supply-chain hijack vector via upstream branch compromise on the external workflow repo. Security-positive change confirming intentionality.
• [permission-reduction] .github/workflows/release.yaml — Previously-floating action references (google-github-actions/run-gemini-cli@v0, actions/upload-artifact@v6, actions/download-artifact@v7) are now pinned to immutable commit SHAs with the major-version tag preserved as a trailing comment. Eliminates the risk of a re-tagged or compromised upstream release silently executing new code in CI. Pins match the established <sha> # <version> convention and Renovate's digest format. Security-positive change.
• [supply-chain] .github/workflows/codeql.yml — Minor-version bumps of security-relevant actions (step-security/harden-runner v2.15.1 → v2.21.1, github/codeql-action/* v4.32.6 → v4.37.9, actions/checkout v6.0.3 → v6.1.0, actions/setup-go v6.2.0 → v6.5.0, softprops/action-gh-release v2.5.3 → v2.6.2) remain SHA-pinned with the version in a trailing comment, matching the existing hardening convention. No permissions: or secrets: blocks were altered in this diff, so blast radius of the new versions is bounded by the existing least-privilege scoping.
• [scope-authorization-implicit] N/A — Authorization inferred from mechanical nature of change (value-only / digest bump). No architectural review required. See also: [protected-path] finding at .github/workflows/.
• [provenance-warning] N/A — Prior review context discarded: provenance validation failed (unverifiable-wrong-app). This review treats all findings as first-time assessments; severity anchoring was skipped for this run.

Previous run (16)

Review

Findings

Info

• [protected-path] .github/workflows/*.yaml|yml — This PR modifies protected paths under .github/, which require human approval. Affected files: .github/workflows/auto-merge.yaml, .github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml. The intent-coherence finding below cites renovate.json (extending github>conforma/.github//config/renovate/renovate.json) as standing authorization for Renovate-generated GitHub Actions updates. Human approval is still required for protected-path changes regardless of authorization evidence.
• [scope-authorization-implicit] N/A — Authorization inferred from the mechanical nature of the change (Renovate-generated GitHub Actions minor version bumps and SHA digest pin additions). Standing authorization is provided by the repository's renovate.json. No architectural review required. See also: [protected-path] finding above.
• [provenance-warning] N/A — Prior review context discarded: provenance validation failed with PRIOR_REVIEW_PROVENANCE=unverifiable-wrong-app (a prior review comment exists but was created by a different app than the expected reviewer app, so authorship could not be verified). This review treats all findings as first-time assessments; severity anchoring was skipped for this run.

Notes

The diff is purely mechanical: minor version bumps for step-security/harden-runner, actions/checkout, actions/setup-go, github/codeql-action, softprops/action-gh-release (all with corresponding SHA digest updates), and newly-added SHA digest pins for previously-floating references — conforma/github-workflows@main, google-github-actions/run-gemini-cli@v0, actions/upload-artifact@v6, and actions/download-artifact@v7. No permissions: or secrets: blocks were modified. Adding digest pins to previously-unpinned actions is a supply-chain hardening improvement.

Previous run (17)

Review

Findings

High

• [protected-path] .github/workflows/ — All 5 modified files (.github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml) are under the .github/ protected path. This Renovate PR bumps GitHub Actions to newer minor versions (actions/checkout v6.0.2→v6.1.0, actions/setup-go v6.2.0→v6.5.0, github/codeql-action v4.32.4→v4.37.7, softprops/action-gh-release v2.5.0→v2.6.2, step-security/harden-runner v2.15.0→v2.21.0) with proper SHA pinning, but has no linked issue authorizing the changes to governance/infrastructure files. Human approval is required for all protected-path modifications.
  Remediation: A human reviewer must approve changes to files under .github/. Consider linking a tracking issue for CI dependency update batches.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (18)

Review

Findings

High

• [protected-path] .github/workflows/codeql.yml — This PR modifies 5 files under the protected .github/ path: .github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml. The PR has no linked issue justifying changes to these governance/infrastructure files. Human approval is required for all protected-path changes. Note: renovate.json configuration authorizes Renovate dependency updates to these paths, and the PR body documents the specific version bumps being applied (actions/checkout v6.0.2→v6.1.0, actions/setup-go v6.2.0→v6.5.0, github/codeql-action v4.32.4→v4.37.7, softprops/action-gh-release v2.5.0→v2.6.2, step-security/harden-runner v2.15.0→v2.20.1).
  Remediation: Obtain human review and approval for these CI/CD workflow changes.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (19)

Review

Findings

High

• [protected-path] .github/workflows/* — All 5 changed files are under the .github/ protected path (.github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml). This PR has no linked issue justifying changes to governance/infrastructure files. While the repository has a renovate.json configuration (extending github>conforma/.github//config/renovate/renovate.json) and the PR is authored by renovate[bot], human approval is always required for protected-path changes. The version pin updates themselves appear correct — each action is pinned by full commit SHA with a matching version comment, no permissions were added or changed, and no workflow logic was modified.
  Remediation: A human reviewer should verify these GitHub Actions version bumps are expected and approve the PR.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (20)

Review

Findings

High

• [protected-path] .github/workflows/codeql.yml — All 5 changed files (.github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml) are under the protected .github/ path. This PR has no linked issue providing explicit justification for modifying governance/infrastructure files. While the changes are mechanical GitHub Actions version bumps generated by Renovate (authorized via renovate.json), human approval is always required for protected-path changes.
  Remediation: A human maintainer should review and approve these workflow changes. The version bumps are standard Renovate-managed dependency updates for well-known GitHub Actions.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (21)

Review

Findings

High

• [protected-path] .github/workflows/* — All 5 changed files are under .github/, a protected path requiring human approval. This PR is an automated Renovate dependency update bumping pinned GitHub Actions versions (actions/checkout v6.0.2→v6.1.0, actions/setup-go v6.2.0→v6.5.0, github/codeql-action v4.32.4→v4.37.5, softprops/action-gh-release v2.5.0→v2.6.2, step-security/harden-runner v2.15.0→v2.20.0). All actions remain pinned by full commit SHA, which is the recommended supply-chain security practice. No linked issue provides explicit authorization for modifying these governance/infrastructure files. Renovate is configured via renovate.json in the repository root. Affected files: .github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml.
  Remediation: Human review and approval required for protected-path changes.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

Previous run (22)

Review

Findings

High

• [protected-path] .github/workflows/* — All 5 modified files are under .github/, a protected path requiring human approval. No linked issue provides formal authorization for these changes. The repository has a renovate.json configuration authorizing Renovate bot to manage dependency updates, and the PR description documents each version bump (actions/checkout v6.0.2→v6.1.0, actions/setup-go v6.2.0→v6.5.0, github/codeql-action v4.32.4→v4.37.4, softprops/action-gh-release v2.5.0→v2.6.2, step-security/harden-runner v2.15.0→v2.20.0). All action references use pinned SHA hashes. No correctness or security findings were identified — the version bumps are mechanically sound. Human approval is required for protected-path changes regardless of automation source.
  Remediation: A human maintainer should review and approve the CI workflow version bumps.

Previous run (23)

Review

Findings

High

• [protected-path] .github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml — All 5 changed files are under the .github/ protected path. The PR has no linked issue authorizing these modifications. Human approval is always required for protected-path changes. The repository's renovate.json authorizes Renovate to manage dependency updates, and the version bumps (actions/checkout v6.0.2 to v6.1.0, actions/setup-go v6.2.0 to v6.5.0, github/codeql-action v4.32.4 to v4.37.3, softprops/action-gh-release v2.5.0 to v2.6.2, step-security/harden-runner v2.15.0 to v2.20.0) are consistent across all workflow files with properly pinned commit SHAs.
  Remediation: A human maintainer must review and approve these workflow changes.

Previous run (24)

Looks good to me

Previous run (25)

Review

Approve — standard Renovate dependency update; all changes are minor version bumps for GitHub Actions with SHA-pinned references.

Changes reviewed

Action	Update	Files
step-security/harden-runner	v2.15.0 → v2.20.0	all 5 workflows
actions/checkout	v6.0.2 → v6.1.0	all 5 workflows
actions/setup-go	v6.2.0 → v6.5.0	pre-merge-ci, push-bundles
github/codeql-action	v4.32.4 → v4.37.1	codeql, scorecards
softprops/action-gh-release	v2.5.0 → v2.6.2	release

Verification

• SHA pinning: All action references use 40-character commit SHA pins with version comments — security best practice maintained.
• Consistency: Each action's SHA is identical across all workflow files where it appears.
• No logic changes: Only uses: version references are updated. No changes to workflow triggers, permissions, step configurations, or environment variables.
• Trusted publishers: All actions are from well-known, established publishers (GitHub official, step-security, softprops).
• Notable security content: The harden-runner v2.16.0 release includes fixes for two medium-severity egress bypass vulnerabilities (GHSA-46g3-37rh-v698, GHSA-g699-3x6g-wm3g).

No findings.

---

Protected paths detected — this PR modifies files under one or more
protected paths. The review agent cannot approve PRs that touch these paths.
A human reviewer must approve this PR.

Protected files in this PR:

• .github/workflows/codeql.yml
• .github/workflows/pre-merge-ci.yaml
• .github/workflows/push-bundles.yaml
• .github/workflows/release.yaml
• .github/workflows/scorecards.yml

---

Labels: PR updates GitHub Actions workflow dependencies

Previous run (26)

Review — Approve ✅

Scope: Automated GitHub Actions dependency update (Renovate)

This PR bumps four GitHub Actions to their latest minor versions across five workflow files. All changes are strictly commit-SHA pin updates with matching version comments — no workflow logic, permissions, steps, or behavioral changes.

Changes verified

Action	From	To	Occurrences
step-security/harden-runner	v2.15.0	v2.20.0	7 (all 5 workflow files)
github/codeql-action	v4.32.4	v4.37.1	4 (codeql.yml, scorecards.yml)
actions/setup-go	v6.2.0	v6.5.0	2 (pre-merge-ci.yaml, push-bundles.yaml)
softprops/action-gh-release	v2.5.0	v2.6.2	1 (release.yaml)

Checks performed

• Hash consistency: Each action uses a single commit SHA across all occurrences — no mixed versions within the same action.
• Pin format: All actions remain pinned to full 40-character commit SHAs with version comments (supply chain security best practice).
• No behavioral changes: No workflow triggers, permissions, step logic, environment variables, or secrets were modified.
• No injection vectors: PR body is standard Renovate template with release notes; no instruction-like patterns detected.

---

Protected paths detected — this PR modifies files under one or more
protected paths. The review agent cannot approve PRs that touch these paths.
A human reviewer must approve this PR.

Protected files in this PR:

• .github/workflows/codeql.yml
• .github/workflows/pre-merge-ci.yaml
• .github/workflows/push-bundles.yaml
• .github/workflows/release.yaml
• .github/workflows/scorecards.yml

Previous run (27)

Review — Approve ✅

PR: #1683 — Update github actions (release-v0.7) (minor)
Author: renovate[bot]
Verdict: Approve — no findings

Summary

Mechanical Renovate bot PR updating pinned GitHub Actions versions across 5 workflow files (14 line changes). All changes are 1:1 SHA pin + version comment replacements with no logic, permission, or configuration modifications.

Updated actions:

Action	From	To
step-security/harden-runner	v2.15.0	v2.20.0
github/codeql-action	v4.32.4	v4.37.0
actions/setup-go	v6.2.0	v6.5.0
softprops/action-gh-release	v2.5.0	v2.6.2

Dimension results

Dimension	Result
Correctness	✅ No findings — verified all 14 changes are exact SHA/version swaps
Security	✅ No findings — no permission, secrets, or injection changes
Intent & coherence	✅ Scope authorization implicit (mechanical dependency bump)
Style & conventions	✅ No findings — value-only changes follow existing format
Docs currency	✅ No documentation surface area
Cross-repo contracts	⏭ Skipped — no exported interfaces modified

---

Protected paths detected — this PR modifies files under one or more
protected paths. The review agent cannot approve PRs that touch these paths.
A human reviewer must approve this PR.

Protected files in this PR:

• .github/workflows/codeql.yml
• .github/workflows/pre-merge-ci.yaml
• .github/workflows/push-bundles.yaml
• .github/workflows/release.yaml
• .github/workflows/scorecards.yml

Previous run (28)

Review

Verdict: ✅ Approve

Summary

This is a Renovate-managed dependency update that bumps four GitHub Actions to their latest minor versions across five workflow files. All changes are pure version-pin replacements (commit SHA + version comment) with no logic, permission, trigger, or configuration changes.

Changes reviewed

Action	From	To	Files
actions/setup-go	v6.2.0	v6.5.0	pre-merge-ci.yaml, push-bundles.yaml
github/codeql-action	v4.32.4	v4.36.3	codeql.yml, scorecards.yml
softprops/action-gh-release	v2.5.0	v2.6.2	release.yaml
step-security/harden-runner	v2.15.0	v2.20.0	codeql.yml, pre-merge-ci.yaml, push-bundles.yaml, release.yaml, scorecards.yml

Verification

• Hash consistency: Each action uses the same pinned SHA across all workflow files where it appears.
• No logic changes: Only uses: lines were modified — no changes to with:, env:, run:, permissions, or triggers.
• No new actions: No previously-unused actions were introduced.
• Supply chain posture: All actions continue to be pinned by full commit SHA with version comments — consistent with the project's existing security practices.

No findings.

---

Protected paths detected — this PR modifies files under one or more
protected paths. The review agent cannot approve PRs that touch these paths.
A human reviewer must approve this PR.

Protected files in this PR:

• .github/workflows/codeql.yml
• .github/workflows/pre-merge-ci.yaml
• .github/workflows/push-bundles.yaml
• .github/workflows/release.yaml
• .github/workflows/scorecards.yml

---

Labels: PR updates GitHub Actions workflow dependencies

Previous run (29)

Looks good to me

Previous run (30)

Review

Findings

High

• [protected-path] .github/workflows/ — All 5 modified files (.github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml) are under the .github/ protected path. This PR has no linked issue providing authorization for modifying governance and infrastructure files. Human approval is required for all protected-path changes.
  Remediation: Link an issue authorizing the workflow updates, or obtain explicit human maintainer approval for these CI/CD configuration changes.

Previous run (31)

Review

Findings

High

• [protected-path] .github/workflows/ — All 5 changed files are under the .github/ protected path (.github/workflows/codeql.yml, .github/workflows/pre-merge-ci.yaml, .github/workflows/push-bundles.yaml, .github/workflows/release.yaml, .github/workflows/scorecards.yml). The PR has no linked issue providing authorization for modifying governance/infrastructure files. Human approval is required for all protected-path changes.
  Remediation: Link this PR to an issue that authorizes the CI workflow updates, or obtain explicit human maintainer approval.

Info

• [sub-agent-failure] N/A — The intent-coherence sub-agent did not return findings: model claude-sonnet-4-5@20250929 not available on deployment.

• [sub-agent-failure] N/A — The style-conventions sub-agent did not return findings: model claude-sonnet-4-5@20250929 not available on deployment.

• [info] The correctness and security sub-agents (opus-tier) completed successfully and found no issues. This is a straightforward Renovate bot update of four GitHub Actions to newer minor versions (actions/setup-go v6.2.0→v6.4.0, github/codeql-action v4.32.4→v4.36.2, softprops/action-gh-release v2.5.0→v2.6.2, step-security/harden-runner v2.15.0→v2.19.4). All references use SHA-pinned versions consistent with existing patterns. No permissions blocks, new actions, or injection patterns were introduced.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 7:40 PM UTC · Completed 7:47 PM UTC

Commit: cd01138 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $2.60

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 1ffbdd1b-af77-4cc4-8290-496f28062b6d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

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

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:02 PM UTC · Completed 3:09 PM UTC

Commit: cd01138 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $2.33

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 1:44 PM UTC · Completed 1:51 PM UTC

Commit: cd01138 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $3.82

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 6:10 AM UTC · Completed 6:19 AM UTC

Commit: f0bdd92 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $3.65

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 11:15 AM UTC · Completed 11:24 AM UTC

Commit: 059bbc1 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $4.79

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:10 AM UTC · Completed 2:16 AM UTC

Commit: 57e0afa · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $2.88

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:32 PM UTC · Completed 2:40 PM UTC

Commit: 5d951a5 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $3.06

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 7:59 AM UTC · Completed 8:12 AM UTC

Commit: 260466a · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.66

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 12:13 PM UTC · Completed 12:24 PM UTC

Commit: 321cfe9 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.45

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 6:29 PM UTC · Completed 6:43 PM UTC

Commit: bcb59f6 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $3.15

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 9:02 AM UTC · Completed 9:17 AM UTC

Commit: 3518741 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $3.19

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:09 AM UTC · Completed 10:22 AM UTC

Commit: e71729e · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.91

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:25 PM UTC · Completed 10:41 PM UTC

Commit: 6ac660e · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $3.42

[fullsend-ai-review]

🤖 Review · ⚠️ Cancelled · Started 3:46 PM UTC · Ended 3:57 PM UTC

Commit: 304ad77 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:59 PM UTC · Completed 4:12 PM UTC

Commit: c6058d7 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.82

[fullsend-ai-review]

See the review comment for full details.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.