Bump the github-actions group across 1 directory with 8 updates

DE
2d ago
+21-21

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

PackageFromTo
gradle/actions/setup-gradle6.3.06.4.0
taiki-e/install-action2.87.202.87.26
actions/upload-artifact7.0.17.0.2
actions/setup-node7.0.07.1.0
actions/download-artifact8.0.18.0.2
github/codeql-action/upload-sarif4.38.24.38.3
jdx/mr-boxington-action1.5.01.7.1
dtolnay/rust-toolchain7e38f4b43b4db5c8dd498af069a4f6196df1d067e2a55d2ffb04f378e9626c28d38b36d230d1e12f

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

Release notes

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

v6.4.0

Highlights

Gradle version support status in the Job Summary

The actions now report the support status of every Gradle version used in a workflow, as job annotations and in the Job Summary (#1057). Thanks to @​ov7a for the contribution.

version kind job annotation version table below the table
End-of-life — two or more major versions behind the latest release warning :warning: expandable section naming the affected release lines, pointing at the Gradle Security Subscription
Out of date — one major behind, or more than two minors behind on the current major notice :information_source: one-line legend pointing at the Gradle release lifecycle docs
Current none — —

Deliberately not reported: patch releases (being on 9.7.0 when 9.7.1 exists is not flagged) and pre-releases (release candidates, milestones and snapshots never produce annotations). The latest Gradle release is determined from the wrapper checksum data already bundled with the action, so no network access is required.

Note that these annotations are emitted independently of the add-job-summary setting: setting add-job-summary: 'never' suppresses the Job Summary itself, but the warning and notice annotations remain.

Gradle itself is now reported in the dependency graph

The dependency-submission action now applies v1.5.0 of the GitHub Dependency Graph Gradle Plugin (up from v1.4.2) (#1069).

The headline change is that the Gradle Build Tool running the build is now reported as an org.gradle:gradle-core dependency, so that GitHub can surface known vulnerabilities in the version of Gradle used to run your build. These are the coordinates that GitHub advisories for the Gradle Build Tool are published against.

Details worth knowing:

  • The entry is always reported as a direct dependency with development scope.
  • It is not affected by the project, configuration or scope filters, so it appears even in graphs that filter aggressively.
  • Expect dependency graphs to gain this one new entry the first time a build runs after upgrading.

A new Gradle signing key, if you use dependency verification

[!IMPORTANT] If your build has dependency verification enabled, you must add a second trusted key before upgrading, or Dependency Graph generation will fail signature verification.

github-dependency-graph-gradle-plugin 1.5.0 is signed with a new Gradle signing subkey, and the key previously documented in our setup guide has been revoked upstream:

... (truncated)

Commits
  • 3f5f9ad Document the new Gradle signing key for dependency verification (#1071)
  • b031f6d [bot] Update dist directory
  • 5bc4175 Bump dependency-graph-gradle-plugin to 1.5.0 (#1069)
  • f3ff59b Combined automated updates: wrapper checksums, npm dependencies, setup-java (...
  • 7927085 Update .tool-versions: node 24.18.0, gradle 9.7.1, java 17 (#1068)
  • c3897a4 [bot] Update dist directory
  • 6b92be1 Update dependencies (#1065)
  • 0d208da [bot] Update dist directory
  • e49d0a3 Report EOL and maintenance status for Gradle versions (#1057)
  • 575435b Use the root-qualified :wrapper task (#1064)
  • Additional commits viewable in compare view

Updates taiki-e/install-action from 2.87.20 to 2.87.26

Release notes

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

2.87.26

  • Update tombi@latest to 1.7.2.

  • Update prek@latest to 0.5.5.

  • Update mise@latest to 2026.10.3.

  • Update kache@latest to 1.0.0.

  • Update hyperfine@latest to 1.21.0.

2.87.25

  • Update uv@latest to 0.12.23.

  • Update mise@latest to 2026.10.2.

  • Update kingfisher@latest to 2.10.0.

  • Update dprint@latest to 0.60.1.

  • Update cargo-semver-checks@latest to 0.51.0.

  • Update cargo-binstall@latest to 1.25.1.

2.87.24

  • Update wasmtime@latest to 49.0.2.

  • Update dprint@latest to 0.59.0.

  • Update cargo-leptos@latest to 0.3.11.

  • Update cargo-insta@latest to 1.49.0.

  • Update cargo-binstall@latest to 1.25.0.

2.87.23

  • Update wasm-tools@latest to 1.261.0.

  • Update uv@latest to 0.12.22.

  • Update trivy@latest to 0.75.0.

  • Update tombi@latest to 1.7.1.

  • Update protoc-gen-connect-openapi@latest to 0.28.0.

  • Update mise@latest to 2026.10.0.

  • Update kingfisher@latest to 2.9.1.

... (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.87.28] - 2026-10-12

  • Update dprint@latest to 0.62.0.

  • Update vacuum@latest to 0.33.0.

  • Update uv@latest to 0.13.0.

  • Update tombi@latest to 1.8.1.

  • Update release-plz@latest to 0.3.171.

  • Update rclone@latest to 1.75.2.

  • Update mise@latest to 2026.10.7.

  • Update cargo-binstall@latest to 1.25.3.

[2.87.27] - 2026-10-09

  • Update vacuum@latest to 0.32.0.

  • Update uv@latest to 0.12.24.

  • Update typos@latest to 1.51.1.

  • Update tombi@latest to 1.7.3.

  • Update syft@latest to 1.54.1.

  • Update release-plz@latest to 0.3.170.

  • Update mise@latest to 2026.10.4.

  • Update kingfisher@latest to 2.11.1.

  • Update hyperfine@latest to 2.0.0.

... (truncated)

Commits

Updates actions/upload-artifact from 7.0.1 to 7.0.2

Release notes

Sourced from actions/upload-artifact's releases.

v7.0.2

What's Changed

  • Improves artifact download retries when the service returns HTTP 429 (rate limiting), including honoring valid Retry-After headers.
  • Updates @​actions/artifact to v6.3.1.

New Contributors

Full Changelog: https://github.com/actions/upload-artifact/compare/v7.0.1...v7.0.2

Commits
  • cf430e0 Merge pull request #822 from actions/tunc-d-prepare-upload-v7-0-2
  • c2acded chore: prepare v7.0.2 release
  • 4687c1b Merge pull request #821 from actions/tunc-d-upload-artifact-package-bump
  • 8cbe1be Bump @​actions/artifact to 6.3.1
  • See full diff in compare view

Updates actions/setup-node from 7.0.0 to 7.1.0

Release notes

Sourced from actions/setup-node's releases.

v7.1.0

What's Changed

Enhancements:

Bug fixes:

Documentation updates:

Dependency updates:

New Contributors

Full Changelog: https://github.com/actions/setup-node/compare/v7.0.0...v7.1.0

Commits
  • 949feb2 Bump eslint from 10.5.0 to 10.11.0 and package.json from 7.0.0 to 7.1.0 (#1635)
  • 7207c4f chore: update dependencies and add license files (#1642)
  • 54337e0 Bump eslint-plugin-n from 18.1.0 to 18.3.0 (#1638)
  • fb54fa8 Bump jest-each from 30.4.1 to 30.5.2 (#1636)
  • 7f84f1d Bump pnpm/action-setup from 6.0.10 to 6.1.0 (#1631)
  • 0c54c7b Bump @​typescript-eslint/parser from 8.62.0 to 8.70.0 (#1615)
  • a829419 Bump @​types/semver from 7.7.1 to 7.8.0 (#1616)
  • 680d1e4 Support absolute paths in node-version-file (#1633)
  • db0fb3a Bump baseline-browser-mapping from 2.10.38 to 2.11.22 (#1629)
  • 94196ee Bump pnpm/action-setup from 6.0.9 to 6.0.10 (#1602)
  • Additional commits viewable in compare view

Updates actions/download-artifact from 8.0.1 to 8.0.2

Release notes

Sourced from actions/download-artifact's releases.

v8.0.2

What's Changed

New Contributors

Full Changelog: https://github.com/actions/download-artifact/compare/v8.0.1...v8.0.2

Commits
  • 9000827 Merge pull request #493 from actions/tunc-d-prepare-download-v8-0-2
  • e455989 Prepare download-artifact v8.0.2
  • a00b90c Merge pull request #492 from actions/tunc-d-download-artifact-package-bump
  • 29bb7ce Update @​actions/artifact to 6.3.1
  • 484a0b5 Update the readme (#473)
  • See full diff in compare view

Updates github/codeql-action/upload-sarif from 4.38.2 to 4.38.3

Release notes

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

v4.38.3

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

4.37.9 - 26 Aug 2026

  • Update default CodeQL bundle version to 2.26.4. #4106

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

... (truncated)

Commits
  • 24c5418 Merge pull request #4214 from github/update-v4.38.3-e0b52dbdc
  • 69e87c5 Add changelog note for #4184
  • 23b6828 Update changelog for v4.38.3
  • e0b52db Merge pull request #4210 from github/henrymercer/pin-python-for-older-clis-in-ci
  • 6b99698 Pin Python 3.13.15 for older CLI versions in multi-language check
  • 63d3d63 Merge pull request #4203 from github/update-bundle/codeql-bundle-v2.27.2
  • 7377a10 Add changelog note
  • c1a30cd Update default bundle to codeql-bundle-v2.27.2
  • d208ec7 Merge pull request #4200 from github/mbg/esm/migrate-pr-checks
  • a71b0c6 Replace __dirname in sync.ts
  • Additional commits viewable in compare view

Updates jdx/mr-boxington-action from 1.5.0 to 1.7.1

Release notes

Sourced from jdx/mr-boxington-action's releases.

v1.7.1: More accurate disk-usage reporting in isolated objects-cache mode

Fixes the disk-usage diagnostics that the post step logs when isolate-objects-cache: true is set. Cache restore and save behavior is unchanged.

Fixed

  • Disk-usage summary for isolate-objects-cache (#60, @​donbeave). The Objects cache sample summary in the post step is now more accurate and more reliable:
    • The action now waits for any sample still in progress and takes one last sample before it prints the summary. Before, the summary could be printed before sampling had finished, so it could miss the final disk usage.
    • When a diagnostic sample fails, the failure no longer replaces the actual result of the cache operation. If the restore or save itself failed, that original error is still the one reported. The summary records the number of sampling failures and a short reason code, such as code:EIO, without including file paths.
    • The archive-size figures now count cache.tar staging files, which are used on Windows runners, as well as cache.tgz.

Full Changelog: https://github.com/jdx/mr-boxington-action/compare/v1.7.0...v1.7.1

v1.7.0: Isolated objects cache and cache key suffixes

Parallel jobs can now save under their own primary keys with cache-key-suffix. On disposable hosted runners, the GitHub objects payload can now run from a private, job-scoped store with isolate-objects-cache. Both inputs are opt-in, so existing workflows are unaffected.

Added

  • cache-key-suffix input (#58, @​donbeave). The suffix is added to the end of the generated primary key, so matrix or parallel jobs save their own entries. It does not change the generated restore prefixes, so any job can still warm-start from another job's compatible entry.

    - uses: jdx/mr-boxington-action@v1
  with:
    cache-key-suffix: ${{ matrix.job }}

    The suffix may only contain ASCII letters, numbers, periods, underscores, and hyphens. The final key must be at most 512 characters. Setting both cache-key-suffix and cache-key is an error, so use cache-key on its own when you supply the full primary key. Explicit restore-keys are used as given.

  • isolate-objects-cache input (#58, @​donbeave). Defaults to false and requires backend: github with github-cache-mode: objects. Setup fails if you enable it with any other backend or mode. When it is on:

    • The live mbx store (MBX_CACHE_DIR) is placed in a private directory under RUNNER_TEMP.
    • On restore, the bundle is imported and then deleted.
    • On save, the action exports a bundle and checks it. It then deletes the isolated store before actions/cache packs its upload archive, so the job doesn't keep two copies on disk at once. Only the exported bundle is saved.
    - uses: jdx/mr-boxington-action@v1
  with:
    github-cache-mode: objects
    isolate-objects-cache: true

    The private directory is cleaned up whether the post step succeeds or fails. Use this mode only on disposable hosted runners. Leave it off on persistent runners that rely on mbx's normal warm store. Use one isolated objects-cache step per job. The bundle path is fixed so the cache version matches across jobs and runs.

    In this mode, the post step also logs disk usage at each stage. It sorts save failures by cause:

    • Another job reserving or finalizing the same key, GitHub cache service 5xx errors, and network failures produce a warning, and the job continues.
    • Running out of disk while staging the archive, or any save result the action can't identify, fails the step.

New Contributors

Full Changelog: https://github.com/jdx/mr-boxington-action/compare/v1.6.0...v1.7.0

v1.6.0: Opt-in cache saves from pull requests and protected branches, plus a remote backend

With the GitHub backend, pull requests and protected branches can now save their own cache entries, so later PR revisions reuse what earlier ones built. A new remote backend uses MBX_REMOTE_* settings exported by earlier steps instead of overwriting them. backend: server now works as an alias of remote, with small behavior changes listed below.

... (truncated)

Changelog

Sourced from jdx/mr-boxington-action's changelog.

Changelog

1.7.2 - 2026-10-10

🐛 Bug Fixes

⚙️ Miscellaneous Tasks

1.7.1 - 2026-10-04

🐛 Bug Fixes

1.7.0 - 2026-10-04

🚀 Features

New Contributors

1.6.0 - 2026-10-02

🚀 Features

  • (cache) opt in to saving from pull requests and protected branches (#48) by @​garysassano in #48
  • add a remote backend that keeps MBX_REMOTE_* settings from earlier steps (#53) by @​jdx in #53

🐛 Bug Fixes

... (truncated)

Commits
  • d0825fb chore: release v1.7.1 (#61)
  • a85e486 fix(cache): await resource samples before reporting (#60)
  • a15673c chore: release v1.7.0 (#59)
  • a8d7af5 feat(cache): isolate objects caching and support key suffixes (#58)
  • 1687e54 chore: release v1.6.0 (#49)
  • 81ec447 build(deps-dev): bump @​types/node from 26.6.1 to 26.6.2 (#54)
  • 277ae0a fix(deps): remediate npm audit findings (#57)
  • 91d7f48 chore(entire): restore lower-cost trail findings (#56)
  • 4371c69 chore(entire): route checkpoints privately and commit agent hooks (#55)
  • 05dba6c feat: add a remote backend that keeps MBX_REMOTE_* settings from earlier step...
  • Additional commits viewable in compare view

Updates dtolnay/rust-toolchain from 7e38f4b43b4db5c8dd498af069a4f6196df1d067 to e2a55d2ffb04f378e9626c28d38b36d230d1e12f

Commits

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

Summary by cubic

Bumps eight GitHub Actions dependencies to their latest releases with no expected behavior changes in these workflows.

  • actions/setup-node adds mise.toml support and absolute-path handling for node-version-file; artifact upload and download actions now retry on HTTP 429 rate limits.
  • gradle/actions/setup-gradle now reports Gradle version support status in the job summary; builds with dependency verification must add a second trusted Gradle signing key.
  • jdx/mr-boxington-action gains opt-in cache-key-suffix and isolate-objects-cache inputs, none of which are enabled in this repo.