chore(deps): bump the github-actions group across 1 directory with 3 updates

[dependabot]

Bumps the github-actions group with 3 updates in the / directory: step-security/harden-runner, github/codeql-action/upload-sarif and docker/setup-buildx-action.

Updates step-security/harden-runner from 2.20.0 to 2.21.0

Release notes

Sourced from step-security/harden-runner's releases.

v2.21.0

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

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

Commits

• 05e3151 Merge pull request #684 from step-security/rc-42
• 0f37afa fix: ignore denied-endpoints on non-enterprise tier
• 93b58ee fix: resolve cache host read-first and never downgrade egress policy
• e7399dd fix: align deny-list mode detection with agent and log when both endpoint inp...
• c16689f test: add denied_endpoints to Configuration fixtures and cover deny-list merge
• 40b99cf Merge pull request #682 from rohan-stepsecurity/rp/feat/codebuild-self-v2
• fedec02 Merge branch 'rc-42' into rp/feat/codebuild-self-v2
• 5361fb1 feat: add build artifacts
• 286474f feat: Support Bravo agent install on CodeBuild runners
• 051ec05 Merge pull request #683 from h0x0er/jatin/deny-list
• Additional commits viewable in compare view

Updates github/codeql-action/upload-sarif from 4.37.4 to 4.37.8

Release notes

Sourced from github/codeql-action/upload-sarif's releases.

v4.37.8

No user facing changes.

v4.37.7

• Update default CodeQL bundle version to 2.26.3. #4085

v4.37.6

• 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

• 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

Changelog

Sourced from github/codeql-action/upload-sarif's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

• Update default CodeQL bundle version to 2.26.3. #4085

4.37.6 - 04 Aug 2026

• 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

4.37.5 - 03 Aug 2026

• 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

4.37.4 - 29 Jul 2026

• 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

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

• 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

4.37.1 - 16 Jul 2026

• 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

4.37.0 - 08 Jul 2026

• 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

4.36.3 - 01 Jul 2026

... (truncated)

Commits

• db488dd Merge pull request #4102 from github/update-v4.37.8-9ee088e13
• 1845f5b Update changelog for v4.37.8
• 9ee088e Merge pull request #4080 from github/henrymercer/studious-giggle
• 1aef003 Address review feedback on overlay disk flags
• 508b83b Merge main into overlay minimum disk feature branch
• d97b342 Merge pull request #4098 from github/mbg/permission-error-as-configuration-error
• 47fa622 Make EACCES a ConfigurationError
• 45693cc Refactor ENOSPC check into isDiskConfigurationError function
• c2fd8f5 Merge pull request #4081 from github/mario-campos/version-cache-to-disk
• c56f48e Log unexpected conditions during caching CLI output
• Additional commits viewable in compare view

Updates docker/setup-buildx-action from 4.2.0 to 4.3.0

Release notes

Sourced from docker/setup-buildx-action's releases.

v4.3.0

• Bump @​docker/actions-toolkit from 0.92.0 to 0.95.0 in docker/setup-buildx-action#595
• Bump brace-expansion from 1.1.13 to 1.1.18 in docker/setup-buildx-action#600
• Bump js-yaml from 5.2.0 to 5.3.0 in docker/setup-buildx-action#585
• Bump postcss from 8.5.10 to 8.5.25 in docker/setup-buildx-action#598
• Bump undici from 6.27.0 to 6.28.0 in docker/setup-buildx-action#601

Full Changelog: docker/setup-buildx-action@v4.2.0...v4.3.0

Commits

• 37fe631 Merge pull request #595 from docker/dependabot/npm_and_yarn/docker/actions-to...
• b5c4f91 [dependabot skip] chore: update generated content
• 3e93b63 build(deps): bump @​docker/actions-toolkit from 0.92.0 to 0.95.0
• e527031 Merge pull request #600 from docker/dependabot/npm_and_yarn/brace-expansion-1...
• c68814b [dependabot skip] chore: update generated content
• 3f891b0 build(deps): bump brace-expansion from 1.1.13 to 1.1.18
• 787db26 Merge pull request #585 from docker/dependabot/npm_and_yarn/js-yaml-5.2.1
• f779368 [dependabot skip] chore: update generated content
• 7d5e604 build(deps): bump js-yaml from 5.2.0 to 5.3.0
• 292c2fb Merge pull request #590 from docker/dependabot/github_actions/actions/setup-n...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

---

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[github-actions]

PR governance metadata gate is not ready for f7099f951574a01f1333cb72a5e48ac91e7f4ea5:

• Branch is BEHIND the base branch; update the branch and re-run checks.
• Required check strix is FAILURE on the current head.

[seonghobae]

Exact-head hosted Strix failure was traced to provider infrastructure: NVIDIA NIM returned repeated HTTP 429 rate limits, later fallback attempts emitted provider failure, and the gate correctly failed closed without authoritative vulnerability evidence. Dependency/security/build checks for f7099f951574a01f1333cb72a5e48ac91e7f4ea5 were otherwise green; the failed Strix job was retried through the normal Actions API. No bypass or source suppression is warranted.

[seonghobae]

Exact-head Checks RCA: strix failed on provider infrastructure, not a source finding. The run records NVIDIA NIM HTTP 429 responses and a fallback provider/protocol failure (LLM Provider NOT provided), then failed closed without authoritative clean evidence. This requires central Strix provider/fallback remediation and a fresh exact-head scan; no source patch was applied to this dependency-only PR.

[seonghobae]

Strix failure triage for current head f7099f951574a01f1333cb72a5e48ac91e7f4ea5: the job log shows NVIDIA NIM 429 Too Many Requests, a fallback lifecycle timeout/no executive report, and fallback openai-direct/gpt-5.6-luna 404 page not found; the gate classified this as provider infrastructure unavailable. No source vulnerability report was emitted. Re-ran failed jobs through the Actions API; merge remains blocked until an exact-head authoritative Strix result and required review are available.