chore: bump the github-actions group with 4 updates

[dependabot]

Bumps the github-actions group with 4 updates: github/codeql-action/init, github/codeql-action/analyze, jdx/mise-action and gradle/actions/setup-gradle.

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

Release notes

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

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/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.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

No user facing changes.

4.36.2 - 04 Jun 2026

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

... (truncated)

Commits

• d1ba80a Merge pull request #4067 from github/update-v4.37.5-1cd4d01d5
• e74600b Update changelog for v4.37.5
• 1cd4d01 Merge pull request #4061 from github/henrymercer/turbo-system
• d2bfc30 Merge pull request #4050 from github/mbg/status/registries
• 68028fc Merge pull request #4062 from github/sam-robson/migrate-enterprise-release-pat
• c29563e ci: use federated enterprise release PAT
• 155e522 Link the PR from the changelog entry
• 2d3b351 Handle network errors when streaming the CodeQL bundle download
• 5d3eb98 Merge pull request #4055 from github/dependabot/npm_and_yarn/npm-minor-203262...
• c5f739b Merge branch 'main' into dependabot/npm_and_yarn/npm-minor-2032624187
• Additional commits viewable in compare view

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

Release notes

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

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/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.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

No user facing changes.

4.36.2 - 04 Jun 2026

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

... (truncated)

Commits

• d1ba80a Merge pull request #4067 from github/update-v4.37.5-1cd4d01d5
• e74600b Update changelog for v4.37.5
• 1cd4d01 Merge pull request #4061 from github/henrymercer/turbo-system
• d2bfc30 Merge pull request #4050 from github/mbg/status/registries
• 68028fc Merge pull request #4062 from github/sam-robson/migrate-enterprise-release-pat
• c29563e ci: use federated enterprise release PAT
• 155e522 Link the PR from the changelog entry
• 2d3b351 Handle network errors when streaming the CodeQL bundle download
• 5d3eb98 Merge pull request #4055 from github/dependabot/npm_and_yarn/npm-minor-203262...
• c5f739b Merge branch 'main' into dependabot/npm_and_yarn/npm-minor-2032624187
• Additional commits viewable in compare view

Updates jdx/mise-action from 4.2.3 to 4.2.4

Release notes

Sourced from jdx/mise-action's releases.

v4.2.4: Reliable locking detection under forced color

A small patch release that fixes locking-support detection when workflows force colored output.

Fixed

Detect mise install --locked reliably under forced color (#580 by @​scop)

When colored output was forced globally (for example via CLICOLOR_FORCE=1), ANSI escape codes in mise install --help prevented the action from matching --locked in the help text, so locking support was reported as unavailable even on versions of mise that supported it.

The help probe now runs with NO_COLOR=1 in its environment, which overrides CLICOLOR_FORCE and guarantees plain-text output for the feature detection — regardless of the surrounding workflow's color settings.

Full Changelog: jdx/mise-action@v4.2.3...v4.2.4

Changelog

Sourced from jdx/mise-action's changelog.

Changelog

---

4.2.4 - 2026-07-28

🐛 Bug Fixes

• locking support detection with force-colored output (#580) by @​scop in #580

---

4.2.3 - 2026-07-24

🐛 Bug Fixes

• export mise path entries to subsequent steps (#575) by @​jdx in #575

---

4.2.2 - 2026-07-24

🐛 Bug Fixes

• (release-plz) exit when git-cliff produces no version bump (#566) by @​jdx in #566
• ensure tar supports Zstd (#569) by @​JackMyers001 in #569

📚 Documentation

• update default value of cache_key_prefix (#570) by @​muzimuzhi in #570

New Contributors

• @​muzimuzhi made their first contribution in #570
• @​JackMyers001 made their first contribution in #569

---

4.2.1 - 2026-07-16

🐛 Bug Fixes

• verify mise downloads with signed checksums (#548) by @​jdx in #548
• exclude PATH from environment export (#556) by @​jdx in #556

🔍 Other Changes

• Enable Entire for Codex (#529) by @​jdx in #529

⚙️ Miscellaneous Tasks

• (ci) automate weekly releases (#557) by @​jdx in #557
• (release) skip ai reviews for release prs (#549) by @​jdx in #549

... (truncated)

Commits

• 7e36c90 chore: release v4.2.4 (#581)
• 493a5fd chore(deps): update jdx/renovate-config digest to d4f71e1 (#585)
• 4f79861 chore(deps): update github/codeql-action action to v4.37.2 (#586)
• 3fb09b2 chore(deps): update jdx/pr-closer action to v1.2.0 (#584)
• 4606f11 chore(deps): update jdx/renovate-config digest to aa7a43b (#582)
• 2319179 chore(deps): update actions/checkout action to v7.0.1 (#583)
• b4fa3f8 fix: locking support detection with force-colored output (#580)
• c3c9861 chore(deps): lock file maintenance (#579)
• See full diff in compare view

Updates gradle/actions/setup-gradle from 6.2.0 to 6.3.0

Release notes

Sourced from gradle/actions/setup-gradle's releases.

v6.3.0

Highlights

Enhanced Caching: Windows fixes and a cache-protocol bump

This release updates gradle-actions-caching to v1.0.0 (up from v0.7.0), which fixes two significant caching defects, both most visible on Windows:

• Cache entries failed to store at all on Windows.. Every entry failed with Path Validation Error: Path(s) specified in the action for caching do(es) not exist, even though the Gradle User Home was fully intact. Nothing was stored, so every downstream job ran against an empty Gradle User Home. The cause was a nested, unpatched copy of @actions/glob combined with a silently swallowed require() in the bundle, which left Windows path separators unnormalized.

• Cache cleanup deleted instrumented jars that were in use. A bug in key hashing for paths shorter than 64 characters made cleanup judge freshly created caches/jars-9 entries as unused and remove them, so the instrumented-jars entry was never saved and every job re-instrumented its classpaths.

  Also included: cache entry names are now consistent between the save and restore reports — restore previously fell back to showing the raw glob pattern (e.g. /home/runner/.gradle/caches/modules-*/files-*/*/*/*/*/) instead of dependencies.

[!IMPORTANT] Existing cache entries are invalidated by this release. The cache protocol version was bumped to v2, so the first run after upgrading will be a cache miss and will repopulate the cache. No configuration changes are required.

Basic caching warns instead of failing silently

The basic (open-source) caching provider now emits a warning and reports (Entry not saved: save failed) in the Job Summary when a cache save fails, rather than reporting success (#1028).

Dependency submission works with Isolated Projects

dependency-submission now disables Isolated Projects via a promoted property, so dependency graph generation works on builds that enable it (#1025). Thanks to @​reinsch82 for the contribution.

Updated defaults

• Injected Develocity Gradle plugin: 4.4.2 → 4.5.0
• 36 new known-good wrapper checksums added for wrapper-validation

What's Changed

• Render configuration-cache status in the caching Job Summary by @​bigdaz in gradle/actions#989
• Update gradle-actions-caching library to v0.8.0 by @​bot-githubaction in gradle/actions#993
• Support experimental project-entry caching (configuration-cache + build-logic) by @​bigdaz in gradle/actions#994
• Update gradle-actions-caching library to v0.9.0 by @​bot-githubaction in gradle/actions#996
• Disable Isolated Projects via promoted property in dependency-submission by @​reinsch82 in gradle/actions#1025
• Add Windows coverage for caching via a new smoke-test suite by @​bigdaz in gradle/actions#1027

... (truncated)

Commits

• 9c97196 Bump the github-actions group across 2 directories with 9 updates (#1024)
• 760e4a4 Bump the npm-dependencies group across 1 directory with 2 updates (#1037)
• 73e4c42 Update gradle-actions-caching library to v1.0.0 (#1029)
• a9d1438 Add dependabot ignore rules for TypeScript 7.x and @​types/node 25.x/26.x
• 68f3700 [bot] Update dist directory
• 5971332 Bump Gradle Wrapper to 9.6.1, wrapper checksums, and Develocity plugin to 4.5...
• b5bc804 [bot] Update dist directory
• dcbab4e Bump npm-dependencies group with TypeScript 6.0.3, @​types/node 24.x, and secu...
• ca8d957 Move non-smoke restore-gradle-home tests back to the integ-test suite (#1032)
• 4318659 [bot] Update dist directory
• 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