Skip to content

chore(deps): bump the actions group across 1 directory with 4 updates - #66

Merged
hyperpolymath merged 1 commit into
mainfrom
dependabot/github_actions/actions-b7a5b7c580
Nov 5, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
dependabot/github_actions/actions-b7a5b7c580

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the actions group with 4 updates in the / directory: github/codeql-action/init, github/codeql-action/analyze, hyperpolymath/cicd-squabbler/.github/actions/squabble and step-security/harden-runner.

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

Release notes

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

v4.39.1

  • Update default CodeQL bundle version to 2.27.3. #4256

v4.39.0

  • 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
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
  • 9b32540 Merge pull request #4257 from github/update-v4.39.1-c5a2f4b0f
  • b5e1ed9 Trigger workflows
  • 20f5ec3 Update changelog for v4.39.1
  • c5a2f4b Merge pull request #4245 from github/henrymercer/graduate-overlay-trap-caching
  • 61a5a80 Merge pull request #4256 from github/update-bundle/codeql-bundle-v2.27.3
  • 3dd33f8 Merge pull request #4249 from github/mbg/upload-improvements-for-4223
  • b96e339 Change comment for getConfig call in upload-sarif
  • 7fa4518 Use shouldSkipSarifUpload in analyze-action.ts
  • a69c7cb Document that setting the env vars to false takes precedence
  • 74ddcd9 Fix typo in comment
  • Additional commits viewable in compare view

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

Release notes

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

v4.39.1

  • Update default CodeQL bundle version to 2.27.3. #4256

v4.39.0

  • 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
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
  • 9b32540 Merge pull request #4257 from github/update-v4.39.1-c5a2f4b0f
  • b5e1ed9 Trigger workflows
  • 20f5ec3 Update changelog for v4.39.1
  • c5a2f4b Merge pull request #4245 from github/henrymercer/graduate-overlay-trap-caching
  • 61a5a80 Merge pull request #4256 from github/update-bundle/codeql-bundle-v2.27.3
  • 3dd33f8 Merge pull request #4249 from github/mbg/upload-improvements-for-4223
  • b96e339 Change comment for getConfig call in upload-sarif
  • 7fa4518 Use shouldSkipSarifUpload in analyze-action.ts
  • a69c7cb Document that setting the env vars to false takes precedence
  • 74ddcd9 Fix typo in comment
  • Additional commits viewable in compare view

Updates hyperpolymath/cicd-squabbler/.github/actions/squabble from 14f853fde902ab2d7631070d87a9dc9122e01013 to 395f16cc59fa9d2c3cacde7d8fd926c0962ac280

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
  • 395f16c fix: qualify zero-job and native-lock diagnosis against exact source (#151)
  • 7744f6d Update crates/squabble-core/src/chains.rs
  • dcc794f Update crates/squabble-core/src/chains.rs
  • 1fd9db9 fix(proofs): configure Why3 in the standalone Creusot workspace
  • eeec5ed fix(ci): apply the official source-bound actions lock candidate
  • e324a75 fix(chains): qualify moved dependencies through exact pinned routes
  • 79ad298 docs(startup): clarify attribution, lock verification, and API validation con...
  • b7a5511 fix: bind startup diagnosis to observed jobs and immutable source
  • 1728429 ci: reject contradictory zero-job evidence (#150)
  • 514fc78 docs(startup): document jobs field validation errors in parse_job_count
  • Additional commits viewable in compare view

Updates step-security/harden-runner from 2.22.1 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

v2.22.2

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

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
  • dc2769a Merge pull request #707 from step-security/rc-45
  • ab0b273 Merge pull request #706 from h0x0er/rc-45
  • 03ccff8 Remove agent-preinstalled skip for third-party runners
  • 815e48d Skip agent install and post-step cleanup when agent is already installed
  • See full diff in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Oct 28, 2026
@coderabbitai

coderabbitai Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

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: ASSERTIVE
  • Plan: Advanced
  • Run ID: c8025ef4-4498-4b63-9d1a-a86d7ae63382

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

@dependabot dependabot Bot changed the title chore(deps): bump the actions group with 4 updates chore(deps): bump the actions group across 1 directory with 4 updates Nov 4, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions-b7a5b7c580 branch from db73b87 to 917fa6f Compare November 4, 2026 10:16

Copy link
Copy Markdown
Owner

@dependabot rebase

Please refresh this existing dependency PR against current main before merge. The latest main also contains the independently qualified scanner correction in #68; the old PR-head checks do not qualify that combined tree. Preserve the three full-SHA workflow updates and existing hard gates. I will check the refreshed head, exact source pins, current CodeQL/Rust/K9/DEED results and ordinary merge rules before merging.

Bumps the actions group with 4 updates in the / directory: [github/codeql-action/init](https://github.com/github/codeql-action), [github/codeql-action/analyze](https://github.com/github/codeql-action), [hyperpolymath/cicd-squabbler/.github/actions/squabble](https://github.com/hyperpolymath/cicd-squabbler) and [step-security/harden-runner](https://github.com/step-security/harden-runner).


Updates `github/codeql-action/init` from 4.38.3 to 4.39.1
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@24c5418...9b32540)

Updates `github/codeql-action/analyze` from 4.38.3 to 4.39.1
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@24c5418...9b32540)

Updates `hyperpolymath/cicd-squabbler/.github/actions/squabble` from 14f853fde902ab2d7631070d87a9dc9122e01013 to 395f16cc59fa9d2c3cacde7d8fd926c0962ac280
- [Release notes](https://github.com/hyperpolymath/cicd-squabbler/releases)
- [Changelog](https://github.com/hyperpolymath/cicd-squabbler/blob/main/CHANGELOG.adoc)
- [Commits](hyperpolymath/cicd-squabbler@14f853f...395f16c)

Updates `step-security/harden-runner` from 2.22.1 to 2.22.3
- [Release notes](https://github.com/step-security/harden-runner/releases)
- [Commits](step-security/harden-runner@ccd8616...46b06ce)

---
updated-dependencies:
- dependency-name: github/codeql-action/analyze
  dependency-version: 4.39.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: github/codeql-action/init
  dependency-version: 4.39.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: hyperpolymath/cicd-squabbler/.github/actions/squabble
  dependency-version: 1ab1507a424c9edfe6cb53dea4e33a2f3cc558e3
  dependency-type: direct:production
  dependency-group: actions
- dependency-name: step-security/harden-runner
  dependency-version: 2.22.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions-b7a5b7c580 branch from 917fa6f to d0d977e Compare November 4, 2026 23:09
@sonarqubecloud

sonarqubecloud Bot commented Nov 4, 2026

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath merged commit b9ab55c into main Nov 5, 2026
22 of 23 checks passed
@hyperpolymath
hyperpolymath deleted the dependabot/github_actions/actions-b7a5b7c580 branch November 5, 2026 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant