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

[dependabot]

Bumps the github-actions group with 10 updates in the / directory:

Package	From	To
step-security/harden-runner	2.20.0	2.21.0
astral-sh/setup-uv	9.0.0	10.0.1
bridgecrewio/checkov-action	12.3115.0	12.3117.0
github/codeql-action/upload-sarif	4.37.5	4.37.7
github/codeql-action/init	4.37.5	4.37.7
github/codeql-action/autobuild	4.37.5	4.37.7
github/codeql-action/analyze	4.37.5	4.37.7
actions/attest-build-provenance	4.1.1	4.2.2
actions/attest	4.2.1	4.2.2
taiki-e/install-action	2.85.7	2.86.1

Updates step-security/harden-runner from 2.20.0 to 2.21.0
Updates astral-sh/setup-uv from 9.0.0 to 10.0.1

Release notes

Sourced from astral-sh/setup-uv's releases.

v10.0.1 🌈 Tolerate transient manifest timeouts

Changes

Thank you @​arguile- for making this action more resilient.

🐛 Bug fixes

• Tolerate transient manifest timeouts @​arguile- (#1016)

🧰 Maintenance

• chore: update known checksums for 0.12.4 @github-actions[bot] (#1017)

📚 Documentation

• docs: update version references to v10.0.0 @github-actions[bot] (#1014)

v10.0.0 🌈 Disable automatic caching for sensitive events and new QOL features

Changes

Another breaking release, directly after v9.0.0 but we think the added security justifies that.

Extra security by default

If you use the default enable-cache: auto this will now DISABLE THE CACHE to protect against cache poisoning for the following events:

• pull_request_target
• workflow_run
• release

You can read the full reasoning in astral-sh/setup-uv#984

version: latest-known

- name: Install the latest version of uv known to setup-uv
  uses: astral-sh/setup-uv@v10.0.0
  with:
    version: "latest-known"

This will now install the latest version with a checksum that is known by this action. The known uv checksums are automatically updated but will take a release of this action to take effect. You won't be always using the latest & greatest but you will have an extra level of security.

Read python version from .tool-versions

- name: Install uv based on the version defined in .tool-versions and also set python
  uses: astral-sh/setup-uv@v10.0.0
  with:
    version-file: "pyproject.toml"
</tr></table> 

... (truncated)

Commits

• 20cfd1b chore: update known checksums for 0.12.4 (#1017)
• d73a0ca Tolerate transient manifest timeouts (#1016)
• ae3b92d docs: update version references to v10.0.0 (#1014)
• ae62891 chore(deps): roll up Dependabot updates (#1013)
• f9cdb47 Reject paths in .tool-versions (#1007)
• 4f6036f Require pull requests for Dependabot rollups (#1005)
• 8d6402c chore(deps): roll up Dependabot updates (#1004)
• 46f427b Read Python version from .tool-versions (#996)
• 8ed89c5 ci: pin Alpine container image (#995)
• 8473c7f chore(deps): roll up Dependabot updates (#994)
• Additional commits viewable in compare view

Updates bridgecrewio/checkov-action from 12.3115.0 to 12.3117.0

Commits

• 1246d92 Bump checkov container version to 3.3.11
• 358405d Bump checkov container version to 3.3.10
• See full diff in compare view

Updates github/codeql-action/upload-sarif from 4.37.5 to 4.37.7

Release notes

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

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

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

• ff2f1c6 Merge pull request #4093 from github/update-v4.37.7-be7a3dbb8
• 951a133 Update changelog for v4.37.7
• be7a3db Merge pull request #4087 from github/dependabot/npm_and_yarn/npm-minor-0aa561...
• 9310334 Merge pull request #4086 from github/mbg/thread-action-state-to-codeql
• b4d8a54 Rebuild
• ab5db25 Bump the npm-minor group across 1 directory with 8 updates
• 38055a3 Drop logger from databaseInitCluster in interface
• 1f87aed Merge pull request #4085 from github/update-bundle/codeql-bundle-v2.26.3
• dc1b98a Make logger available to getCodeQLForCmd
• 6f0220e Merge pull request #4084 from github/navntoft/bump-undici
• Additional commits viewable in compare view

Updates github/codeql-action/init from 4.37.5 to 4.37.7

Release notes

Sourced from github/codeql-action/init's releases.

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

Changelog

Sourced from github/codeql-action/init'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

• ff2f1c6 Merge pull request #4093 from github/update-v4.37.7-be7a3dbb8
• 951a133 Update changelog for v4.37.7
• be7a3db Merge pull request #4087 from github/dependabot/npm_and_yarn/npm-minor-0aa561...
• 9310334 Merge pull request #4086 from github/mbg/thread-action-state-to-codeql
• b4d8a54 Rebuild
• ab5db25 Bump the npm-minor group across 1 directory with 8 updates
• 38055a3 Drop logger from databaseInitCluster in interface
• 1f87aed Merge pull request #4085 from github/update-bundle/codeql-bundle-v2.26.3
• dc1b98a Make logger available to getCodeQLForCmd
• 6f0220e Merge pull request #4084 from github/navntoft/bump-undici
• Additional commits viewable in compare view

Updates github/codeql-action/autobuild from 4.37.5 to 4.37.7

Release notes

Sourced from github/codeql-action/autobuild's releases.

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

Changelog

Sourced from github/codeql-action/autobuild'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

• ff2f1c6 Merge pull request #4093 from github/update-v4.37.7-be7a3dbb8
• 951a133 Update changelog for v4.37.7
• be7a3db Merge pull request #4087 from github/dependabot/npm_and_yarn/npm-minor-0aa561...
• 9310334 Merge pull request #4086 from github/mbg/thread-action-state-to-codeql
• b4d8a54 Rebuild
• ab5db25 Bump the npm-minor group across 1 directory with 8 updates
• 38055a3 Drop logger from databaseInitCluster in interface
• 1f87aed Merge pull request #4085 from github/update-bundle/codeql-bundle-v2.26.3
• dc1b98a Make logger available to getCodeQLForCmd
• 6f0220e Merge pull request #4084 from github/navntoft/bump-undici
• Additional commits viewable in compare view

Updates github/codeql-action/analyze from 4.37.5 to 4.37.7

Release notes

Sourced from github/codeql-action/analyze's releases.

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

Changelog

Sourced from github/codeql-action/analyze'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

• ff2f1c6 Merge pull request #4093 from github/update-v4.37.7-be7a3dbb8
• 951a133 Update changelog for v4.37.7
• be7a3db Merge pull request #4087 from github/dependabot/npm_and_yarn/npm-minor-0aa561...
• 9310334 Merge pull request #4086 from github/mbg/thread-action-state-to-codeql
• b4d8a54 Rebuild
• ab5db25 Bump the npm-minor group across 1 directory with 8 updates
• 38055a3 Drop logger from databaseInitCluster in interface
• 1f87aed Merge pull request #4085 from github/update-bundle/codeql-bundle-v2.26.3
• dc1b98a Make logger available to getCodeQLForCmd
• 6f0220e Merge pull request #4084 from github/navntoft/bump-undici
• Additional commits viewable in compare view

Updates actions/attest-build-provenance from 4.1.1 to 4.2.2

Release notes

Sourced from actions/attest-build-provenance's releases.

v4.2.2

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

• Bump actions/attest from 4.2.0 to 4.2.1 in the actions-minor group by @​dependabot[bot] in actions/attest-build-provenance#862

Full Changelog: actions/attest-build-provenance@v4.1.1...v4.2.2

Commits

• 4d10147 Bump actions/attest from 4.2.0 to 4.2.1 in the actions-minor group (#862)
• e3fe62e Bump the actions-minor group with 2 updates (#860)
• See full diff in compare view

Updates actions/attest from 4.2.1 to 4.2.2

Release notes

Sourced from actions/attest's releases.

v4.2.2

What's Changed

• Bump @​sigstore/oci from 0.7.1 to 0.7.2 by @​bdehamer in actions/attest#469
• Bump brace-expansion by @​dependabot[bot] in actions/attest#468
• Bump ip-address from 10.2.0 to 10.4.0 by @​dependabot[bot] in actions/attest#467

Full Changelog: actions/attest@v4.2.1...v4.2.2

Commits

• 1e69f48 Bump ip-address from 10.2.0 to 10.4.0 (#467)
• 02787ce Bump brace-expansion (#468)
• 98ac037 bump @​sigstore/oci from 0.7.1 to 0.7.2 (#469)
• See full diff in compare view

Updates taiki-e/install-action from 2.85.7 to 2.86.1

Release notes

Sourced from taiki-e/install-action's releases.

2.86.1

• Fix an issue where oxfmt was　accidentally installed as oxfmt-{target}{exe}. (#1969)

2.86.0

• Support oxfmt. (#1967, thanks @​rami3l)

2.85.14

• Update uv@latest to 0.12.4.

• Update trivy@latest to 0.74.0.

• Update tombi@latest to 1.4.0.

• Update mdbook-mermaid@latest to 0.17.1.

• Update cargo-xwin@latest to 0.23.1.

2.85.13

• Update tombi@latest to 1.3.3.

• Update mise@latest to 2026.8.5.

• Update kingfisher@latest to 1.113.0.

• Update cargo-shear@latest to 1.13.4.

• Update bpf-linker@latest to 0.11.0.

2.85.12

• Update zola@latest to 0.23.3.

• Update wasm-tools@latest to 1.256.0.

• Update tombi@latest to 1.2.10.

• Update syft@latest to 1.51.0.

• Update prek@latest to 0.4.13.

• Update mise@latest to 2026.8.4.

• Update editorconfig-checker@latest to 3.11.1.

• Update cargo-tarpaulin@latest to 0.37.1.

• Update cargo-rdme@latest to 2.2.1.

• Update biome@latest to 2.5.8.

2.85.11

... (truncated)

Changelog

Sourced from taiki-e/install-action's changelog.

Changelog

All notable changes to this project will be documented in this file.

This project adheres to Semantic Versioning.

[Unreleased]

[2.86.6] - 2026-08-23

• Update dprint@latest to 0.56.1.

• Update cargo-lambda@latest to 1.9.2.

• Update biome@latest to 2.5.10.

[2.86.5] - 2026-08-21

• Update zola@latest to 0.23.4.

• Update wasm-tools@latest to 1.257.1.

• Update protoc@latest to 3.36.0.

• Update mise@latest to 2026.8.10.

• Update cargo-dinghy@latest to 0.8.6.

• Update wasmtime@latest to 48.0.0.

[2.86.4] - 2026-08-20

• Update oxfmt@latest to 1.79.0.

• Update mise@latest to 2026.8.8.

• Update martin@latest to 1.14.0.

• Update dprint@latest to 0.56.0.

• Update cargo-about@latest to 0.9.2.

• Update biome@latest to 2.5.9.

[2.86.3] - 2026-08-18

... (truncated)

Commits

• 288e746 Release 2.86.1
• 6012fb0 Fix oxfmt installation
• b27e114 Release 2.86.0
• 23e8349 Update changelog
• 806f6f7 Support oxfmt on riscv64 Linux
• 57e465d Support oxfmt (#1967)
• decb84f Release 2.85.14
• 1ed90f1 Update uv@latest to 0.12.4
• a2f49bf Update trivy@latest to 0.74.0
• 0d6d274 Update tombi@latest to 1.4.0
• Additional commits viewable in compare view

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[rldyourmnd]

Diagnosed from a fresh run (the original logs had already aged out under the one-day Actions retention, which is estate issue #99).

Four declared-state validators fail, and they are failing correctly:

[FAIL] tool-registry
[FAIL] harden-runner-contract
[FAIL] scorecard-evidence-contract
[FAIL] catalog
validate_all (core): FAIL

This is not a defect in the bump. This repository declares its tool versions in catalog/tools.yml and related contracts, and the validators exist to catch exactly this: workflow pins moving while the declared catalog stays behind. Dependabot updates uses: lines and knows nothing about the catalog, so every grouped action bump in this repository will land red by construction until the catalog is regenerated in the same change.

The bump itself is substantive rather than routine — astral-sh/setup-uv goes v9.0.0 → v10.0.1, a major, and step-security/harden-runner v2.20.0 → v2.21.0 runs with egress-policy: block and an explicit allowed-endpoints list. Both deserve a read before merge, not just a green tick.

Correct fix is one change containing: the bumped pins, the regenerated catalog/tools.yml, the harden-runner and scorecard evidence contracts, and the regenerated docs/generated/* matrices. Filed as a standing gap so this does not have to be re-derived on every bump.

[rldyourmnd]

Closing, and the reason is broader than this PR.

It cannot merge on its own terms. Four declared-state validators fail because Dependabot moves uses: pins while catalog/tools.yml and the harden-runner and scorecard evidence contracts stay behind. That is tracked as #37; the validators are correct and the gap is that no supported path exists for a bump to arrive with its regenerated declaration.

And while it stays open it breaks every other pull request. The pr-hygiene fixtures run commitlint across the repository's open pull requests. This PR's message — chore(deps): bump the github-actions group across 1 directory with 10 updates followed by Dependabot's ten-entry body — fails those rules, so fixture-pr-hygiene, fixture-pr-hygiene-explicit, cleanup-pr-hygiene and evidence-pr-hygiene go red on unrelated changes. That was diagnosed on #38, which touches only Python scripts and inherited the same four failures.

So the cost of leaving it open is not a stale red PR, it is a shared fixture that reports failure for whoever opens the next change.

Nothing is lost. Dependabot regenerates this group on its weekly schedule. When #37 is closed the regenerated bump will land green, and the bump itself deserves a read at that point rather than a merge — astral-sh/setup-uv v9.0.0 → v10.0.1 is a major, and step-security/harden-runner v2.20.0 → v2.21.0 runs with egress-policy: block and an explicit endpoint allowlist.

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

[rldyourmnd]

Correction to my closing comment: the second reason I gave was wrong, and it was my own mistake.

I wrote that leaving this PR open breaks every other pull request, because pr-hygiene fixtures ran commitlint over this PR's message. That is not what happened. The branch I was testing with had accidentally been cut from this PR's commit rather than from main, so it carried the bump — and therefore failed the same four catalog validators. I read my own contamination as evidence about this PR.

Checked properly afterwards:

• main at f66a2070 passes static validators — its last run was green.
• A branch cut cleanly from main with unrelated changes does not inherit these failures.
• So this PR was never poisoning anyone else's checks.

The first reason stands and is why this stays closed. catalog/tools.yml records harden-runner v2.20.0 and setup-uv v9.0.0 while the bump writes v2.21.0 and v10.0.1 into the pin comments, and tool-registry correctly refuses the disagreement:

ci.yml:38: pin comment says 'v2.21.0' but catalog/tools.yml records current_version 'v2.20.0'
ci.yml:62: pin comment says 'v10.0.1' but catalog/tools.yml records current_version 'v9.0.0'

Dependabot writes one half of that pair and nothing writes the other, which is #37. When that is closed the regenerated bump lands green.

Recording the correction rather than editing the original, because a wrong diagnosis that quietly disappears is worse than one that is visibly retracted.