[dependabot]

Bumps the actions group with 7 updates in the / directory:

Package	From	To
hyperpolymath/cicd-squabbler/.github/actions/squabble	541ab9bc21a776d55eb46611877521a824d6319c	79d7dbacc8a02b4a4388b4a36fe46893b5b7ce73
github/codeql-action/init	4.39.1	4.39.3
github/codeql-action/analyze	4.39.1	4.39.3
github/codeql-action/upload-sarif	4.39.1	4.39.3
step-security/harden-runner	2.22.2	2.22.3
taiki-e/install-action	2.87.30	2.90.1
hyperpolymath/panic-attack/.github/workflows/scan-and-report.yml	b22bed4f8c6dce82fde639aa0dab9ce79d1006f5	f2a6a70eaec0cb02331e3264e05f185b5faab0f7

Updates hyperpolymath/cicd-squabbler/.github/actions/squabble from 541ab9bc21a776d55eb46611877521a824d6319c to 79d7dbacc8a02b4a4388b4a36fe46893b5b7ce73

Changelog

Sourced from hyperpolymath/cicd-squabbler/.github/actions/squabble's changelog.

== Changelog

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

The format is based on https://keepachangelog.com/en/1.1.0/[Keep a Changelog], and this project adheres to https://semver.org/spec/v2.0.0.html[Semantic Versioning].

=== [Unreleased]

==== Added

• scripts/local-verify.sh (and just local-verify) — runs every gate CI runs, locally, and leaves one bundle (SUMMARY.txt inside a timestamped $TMPDIR directory) carrying per-step status, the errors extracted from each log, the toolchain identity and the before/after worktree state. It writes nothing into the repository, and it delegates installation to scripts/install-toolchain.sh so nothing it installs is unverified. Status vocabulary is the estate's: PASS/FAIL/VOID/SKIP/KNOWN, where VOID ("no check was performed") and SKIP are never passes, and a KNOWN pre-existing failure must be the single failure in the run to be recognised at all. --only <ids> runs a subset (deselected steps are recorded SKIP, never PASS) and --check reports the toolchain and the plan without running a step or writing a ledger. Written because the new modules below were authored without a reachable Rust toolchain. They type-check on CI but have not been executed: Cargo fmt fails first, and the Cargo test job does not start. That failure is inherited: main is not fmt-clean, and the 7 unformatted workspace files it carries are repaired by #144 (and identically by #143). None of the files this change adds or modifies is unformatted. Merge one of those two first, rebase, and fmt passes on its own — only then do clippy and the tests execute.
• tests/local_verify_test.sh — 31 planted controls for the harness above: no toolchain (VOID, exit 2), all-green (exit 0), a planted compile error (its diagnostic and file:line extracted), a fmt diff, a failing assertion (both sides extracted), --only, --check, a missing jq (VOID, never PASS), an unchanged worktree, and exactly one documented status per ledger row. No Rust, no network, no token: bash tests/local_verify_test.sh. Two of its own first-draft cases were wrong and were fixed, not worked around: the bare PATH fixture omitted dirname, so the script under test resolved its repository root to / and two VOID cases passed for the wrong reason; and one case piped the script into grep -q, which exits at the first match and killed the writer with SIGPIPE, which pipefail then reported as the plan being missing.
• squabble_core::execution — the execution-phase classifier. fight knew only that a check was red, so a job that died in runner setup or lock resolution was attributed by the workflow's shape (a code fixer, a security scan, an upstream owner) rather than as provisioning. The module classifies step evidence into the five outcomes an estate report must keep distinct — not started, preflight, prerequisite missing, policy step failed, verified — with a fail-closed Unclassified carrying one of five reasons, and a Handoff naming who must act. Signatures are host-supplied (no step name is

... (truncated)

Commits

• 79d7dba fix: preserve @ in workflow filenames and record qualified proof receipt (#152)
• 36a150d refactor(forge): separate workflow-entry parsing from repository metadata
• 4534cf1 docs: scope Creusot receipts to their source and counted evidence
• 4ee55d1 style: apply hosted formatter output for workflow population guards
• 81d8103 fix: require complete workflow populations before coordinate attribution
• ac26aa5 test: use extracted workflow paths in two-hop chain controls
• 99a9859 fix: resolve run ref suffixes against exact source filenames
• e54ffe6 fix: preserve workflow filenames containing @ in startup diagnosis
• 395f16c fix: qualify zero-job and native-lock diagnosis against exact source (#151)
• 7744f6d Update crates/squabble-core/src/chains.rs
• Additional commits viewable in compare view

Updates github/codeql-action/init from 4.39.1 to 4.39.3

Release notes

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

v4.39.3

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

v4.39.2

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

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.39.3 - 04 Nov 2026

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

4.39.1 - 21 Oct 2026

• Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

• 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

4.38.3 - 08 Oct 2026

• 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

4.38.2 - 24 Sept 2026

• Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

• 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

4.38.0 - 09 Sept 2026

• 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

... (truncated)

Commits

• 33d7b85 Merge pull request #4299 from github/update-v4.39.3-064910ba2
• 24393f8 Update changelog for v4.39.3
• 064910b Merge pull request #4297 from github/mbg/update-glob
• f532ac5 Update glob to 14.0.3
• 8cd4dfa Merge pull request #4280 from github/mbg/ci/validate-yaml
• cea289b Return different exit code when a language is not recognised
• 7287bb3 Remove exclude entry that's no longer needed
• 8eb7cdf Use normal .editorconfig pattern
• 160e547 Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
• 913e1bb Merge pull request #4283 from github/sam-robson/decode-diff-informed-sarif-uris
• Additional commits viewable in compare view

Updates github/codeql-action/analyze from 4.39.1 to 4.39.3

Release notes

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

v4.39.3

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

v4.39.2

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

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.39.3 - 04 Nov 2026

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

4.39.1 - 21 Oct 2026

• Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

• 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

4.38.3 - 08 Oct 2026

• 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

4.38.2 - 24 Sept 2026

• Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

• 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

4.38.0 - 09 Sept 2026

• 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

... (truncated)

Commits

• 33d7b85 Merge pull request #4299 from github/update-v4.39.3-064910ba2
• 24393f8 Update changelog for v4.39.3
• 064910b Merge pull request #4297 from github/mbg/update-glob
• f532ac5 Update glob to 14.0.3
• 8cd4dfa Merge pull request #4280 from github/mbg/ci/validate-yaml
• cea289b Return different exit code when a language is not recognised
• 7287bb3 Remove exclude entry that's no longer needed
• 8eb7cdf Use normal .editorconfig pattern
• 160e547 Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
• 913e1bb Merge pull request #4283 from github/sam-robson/decode-diff-informed-sarif-uris
• Additional commits viewable in compare view

Updates github/codeql-action/upload-sarif from 4.39.1 to 4.39.3

Release notes

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

v4.39.3

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

v4.39.2

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

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.39.3 - 04 Nov 2026

• Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

• Update default CodeQL bundle version to 2.27.4. #4284
• Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
• Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

4.39.1 - 21 Oct 2026

• Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

• 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

4.38.3 - 08 Oct 2026

• 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

4.38.2 - 24 Sept 2026

• Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

• 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

4.38.0 - 09 Sept 2026

• 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

... (truncated)

Commits

• 33d7b85 Merge pull request #4299 from github/update-v4.39.3-064910ba2
• 24393f8 Update changelog for v4.39.3
• 064910b Merge pull request #4297 from github/mbg/update-glob
• f532ac5 Update glob to 14.0.3
• 8cd4dfa Merge pull request #4280 from github/mbg/ci/validate-yaml
• cea289b Return different exit code when a language is not recognised
• 7287bb3 Remove exclude entry that's no longer needed
• 8eb7cdf Use normal .editorconfig pattern
• 160e547 Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
• 913e1bb Merge pull request #4283 from github/sam-robson/decode-diff-informed-sarif-uris
• Additional commits viewable in compare view

Updates step-security/harden-runner from 2.22.2 to 2.22.3

Release notes

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

v2.22.3

What's Changed

• Added support for Avrea-hosted runners (enterprise tier)
• Fixed unexpected blocking of allowed connections caused by GitHub’s DNS resolver and outbound proxy experiment on GitHub-hosted Linux runners
• Added a feature flag to disable implicit AWS endpoint allowances on self-hosted Linux runners (enterprise tier)

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

Commits

• 46b06ce Merge pull request #711 from step-security/rc-46
• f82eb4b Merge pull request #710 from h0x0er/jatin/tp-avrea
• 665b85a update agent-self-hosted, agent-bravo to v1.9.5 and agent to v0.18.0
• 80fffe1 detect avrea runners
• See full diff in compare view

Updates taiki-e/install-action from 2.87.30 to 2.90.1

Release notes

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

2.90.1

• Update zizmor@latest to 1.32.0.

• Update uv@latest to 0.13.7.

• Update typos@latest to 1.52.0.

• Update tombi@latest to 1.9.9.

• Update syft@latest to 1.56.0.

• Update mise@latest to 2026.11.0.

• Update kache@latest to 2.0.0.

• Update cargo-nextest@latest to 0.9.151.

2.90.0

• Add fallback: skip input option. This is similar to fallback: none but skip unsupported tools instead of error. (#2052)

• Update vacuum@latest to 0.36.2.

• Update release-plz@latest to 0.4.3.

• Update bpf-linker@latest to 0.13.0.

2.89.1

• Install ld.mold symlink when installing mold on Linux. Previously, only mold binary was installed. (#2050, thanks @​FirelightFlagboy)

• Update parse-dockerfile@latest to 0.1.9.

• Update parse-changelog@latest to 0.6.18.

• Update cargo-minimal-versions@latest to 0.1.38.

• Update cargo-hack@latest to 0.6.46.

2.89.0

• Support yq. (#2036, thanks @​FirelightFlagboy)

• Support mold. (#2044, thanks @​FirelightFlagboy)

• Fix an error when old cargo-binstall had already been installed at non-standard location. (#2048)

• Update wasm-tools@latest to 1.263.0.

• Update wasm-pack@latest to 0.15.1.

• Update wasm-bindgen@latest to 0.2.130.

... (truncated)

Changelog

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

[2.90.1] - 2026-11-04

• Update zizmor@latest to 1.32.0.

• Update uv@latest to 0.13.7.

• Update typos@latest to 1.52.0.

• Update tombi@latest to 1.9.9.

• Update syft@latest to 1.56.0.

• Update mise@latest to 2026.11.0.

• Update kache@latest to 2.0.0.

• Update cargo-nextest@latest to 0.9.151.

[2.90.0] - 2026-11-03

• Add fallback: skip input option. This is similar to fallback: none but skip unsupported tools instead of error. (#2052)

• Update vacuum@latest to 0.36.2.

• Update release-plz@latest to 0.4.3.

• Update bpf-linker@latest to 0.13.0.

[2.89.1] - 2026-11-02

• Install ld.mold symlink when installing mold on Linux. Previously, only mold binary was installed. (#2050, thanks @​FirelightFlagboy)

• Update parse-dockerfile@latest to 0.1.9.

• Update parse-changelog@latest to 0.6.18.

• Update cargo-minimal-versions@latest to 0.1.38.

• Update cargo-hack@latest to 0.6.46.

[2.89.0] - 2026-11-01

• Support yq. (#2036, thanks @​FirelightFlagboy)

• Support mold. (#2044, thanks @​FirelightFlagboy)

• Fix an error when old cargo-binstall had already been installed at non-standard location. (#2048)

• Update wasm-tools@latest to 1.263.0.

... (truncated)

Commits

• c509219 Release 2.90.1
• 4809658 codegen: kache 2.0.0 split binaries
• 2f5a77a Update zizmor@latest to 1.32.0
• 44e3ac1 Update uv@latest to 0.13.7
• 91480af Update typos@latest to 1.52.0
• 1886998 Update tombi@latest to 1.9.9
• d66493d Update syft@latest to 1.56.0
• ae0b89b Update prek manifest
• 773fb6f Update mise@latest to 2026.11.0
• 0a95b08 Update kache@latest to 2.0.0
• Additional commits viewable in compare view

Updates hyperpolymath/panic-attack/.github/workflows/scan-and-report.yml from b22bed4f8c6dce82fde639aa0dab9ce79d1006f5 to f2a6a70eaec0cb02331e3264e05f185b5faab0f7

Changelog

Sourced from hyperpolymath/panic-attack/.github/workflows/scan-and-report.yml's changelog.

== Changelog

=== [Unreleased]

==== Added — +assail --output-format kyaml+ writes a KYAML copy

• With +--output-format kyaml+ and +--output report.json+, +assail+ writes +report.kyaml+ beside the JSON report. The JSON stays the report of record: it is what +--attest+ seals. +--output+ must end in +.json+ (any letter case), and no two of the files written (report, copy, and the +--attest+ sidecar) may be the same file: a symbolic link at any of their paths, or two existing paths that are hard links to one file, is refused before anything is written. So is a path that exists but is not a regular file (a directory, say) or that cannot be looked up, such as a derived name over the filesystem's length limit. These checks run before the writes, so a link swapped in between a check and its write is not caught, and a crash can leave a partial file: the planned generation-directory publish is meant to close both. Other formats are unchanged for +assail+.

==== Fixed — KYAML keys holding a line separator

• KYAML output now escapes U+2028 (LS) and U+2029 (PS) as +\uXXXX+, as it already did for NEL (U+0085). go-yaml, the parser behind +yq+, reads all three as line breaks, so a raw one in a key made the document unparseable by +yq+ and by standards' +kyaml-format.sh+. +crate::yaml+ (serde-saphyr) read these files correctly before and after.

==== Changed — attestation hashes are reproducible JCS

• +assail --attest+ now hashes the intent and evidence records as their JCS (RFC 8785) bytes instead of +serde_json+ struct order, and writes the +.attestation.json+ sidecar itself as I-JSON/JCS. Anyone holding the sidecar can recompute both hashes in any language, for example with +jq -cjS .attestation.intent | sha256sum+.
• The seal gains a +hash_scheme+ field (+jcs-sha256+). The scheme is prefixed to the chain hash, so it is covered by any Ed25519 signature: relabelling a seal as legacy to skip the content check breaks the chain hash.
• +attest verify+ now rehashes the embedded intent and evidence and fails on a mismatch. Before, it checked only that the chain hash matched the three stored digests, so the intent and evidence could be edited after sealing without detection. Sidecars written before this change (no +hash_scheme+) still verify, reported as +not rehashed (legacy hash scheme)+.
• +attest verify+ rejects any digest field that is not exactly 64 lowercase hex characters. Fixed widths keep the legacy and scheme-prefixed chain inputs (192 and 202 bytes) apart; otherwise moving the scheme name into +intent_hash+ would reproduce the signed bytes on the legacy path.

==== Added — KYAML report output

• +--output-format kyaml+ writes reports in KYAML, the estate YAML dialect

... (truncated)

Commits

• f2a6a70 Fix recon's real baseline and simplify ledger verification (#271)
• 9d823cb Replace legacy Python CI helpers with tested Rust equivalents (#270)
• acc7a95 Finish Windows portability review controls without Git-dependent Cargo tests ...
• 858dfeb Fix Windows checkout paths and prevent non-portable mass-panic reports (#268)
• 6d3d52a test(security): annotate intentional hardcoded-password detection fixture (#266)
• db8faea fix(config): require TOML parser in default and HTTP builds (#265)
• d4cef9d chore(deps): bump the rust-minor group across 1 directory with 3 updates (#260)
• 96be279 feat(assail): write a KYAML copy beside the sealed JSON report (#264)
• ebc984d chore(deps): bump the actions group across 1 directory with 4 updates (#252)
• 9943a0c chore(deps): bump toml_edit from 0.23.10+spec-1.0.0 to 0.25.0+spec-1.1.0 (#256)
• 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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: hyperpolymath/verisimdb
• Branch: main
• File: .coderabbit.yaml
• Commit: 137045a
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: d54bb518-5712-43cb-bd17-f299195236fe

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

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

Share

• X
• Mastodon
• Reddit
• LinkedIn

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud