Skip to content

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

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-ed6f7802e2
Open

chore(deps): bump the github-actions group across 1 directory with 5 updates#318
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-ed6f7802e2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 1, 2026

Copy link
Copy Markdown
Contributor

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

Package From To
github/codeql-action/init 4.38.3 4.39.1
actions/setup-java 6.0.1 6.1.0
github/codeql-action/analyze 4.38.3 4.39.1
jdx/mise-action 5.1.2 5.2.4
nais/deploy/actions/deploy fa754451577294aae42872a69b888b3470478ec1 3944168fd20b7eea3818e97de3810f74b54c78ff

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

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

... (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 actions/setup-java from 6.0.1 to 6.1.0

Release notes

Sourced from actions/setup-java's releases.

v6.1.0

What's Changed

New Contributors

Full Changelog: actions/setup-java@v6.0.1...v6.1.0

Commits
  • b843ebf Support Maven plugin repositories in generated settings.xml (#1286)
  • 2a69be2 feat: support Maven server credential origins (#1282)
  • d0e6e4d chore(deps): bump the monthly-npm-updates group with 13 updates (#1276)
  • b24925b chore(deps): bump undici from 6.28.0 to 6.29.0 (#1274)
  • 47b3648 Support Temurin JEP 322 patch versions like 26.0.2.1+1 (#1270) (#1279)
  • 74920aa Prefer Zulu 4-segment hotfix builds when resolving version ranges (#1278)
  • a78ec39 Stop GPG agent before removing signature-verification home (#1273)
  • 97c5a5e Support Temurin on Linux RISC-V (#1269)
  • 1aa87b6 Preserve compound Liberica build versions from .sdkmanrc (#1268)
  • See full diff 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.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

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

... (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 jdx/mise-action from 5.1.2 to 5.2.4

Release notes

Sourced from jdx/mise-action's releases.

v5.2.4: Reuse cached signed checksums when restoring mise

Jobs that restore mise from the cache no longer have to download its signed checksums from GitHub on every run, so a network failure at that step no longer fails a job that otherwise restored correctly.

Fixed

  • Restoring a cached mise no longer needs a network download of the checksums. The action checks the cached mise binary against the signed SHASUMS256.txt and its .minisig. Before this release it downloaded both files from GitHub on every run, even when the cache restored correctly. When that download failed, for example after repeated curl errors, the job failed. Now, once the signature checks out, the action saves both files as SHASUMS256-<version>.txt and .minisig in <mise_dir>/bin, which is part of the mise cache. On later runs it reads them from the restored cache and checks the minisign signature again before using them. If the files are missing, corrupt or tampered with, the action downloads them as it did before. There are no new inputs. (#708 by @​jdx)
    • Caches saved by earlier versions don't contain these files. The main cache is only saved on a cache miss, so runs keep downloading the checksums until the cache is saved again or its key changes.

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

v5.2.3: Faster cache key computation in large workspaces

The cache key no longer comes from searching the whole workspace for mise config files. In repos that already contain node_modules or vendor/bundle, this removes a delay of several minutes in "Restoring mise cache".

Fixed

  • "Restoring mise cache" no longer takes minutes after installing dependencies. To build the cache key, the action used to match about 25 **/… glob patterns. That meant it walked every subdirectory of the workspace, including node_modules and vendor/bundle, before checking the cache at all. When the action ran after a step like pnpm install or ruby/setup-ruby with bundler-cache: true, this could take 3–7 minutes. The action now looks for mise config files the same way mise does: only in the working directory and each parent directory up to the workspace root. It checks for mise.toml, .mise.toml, .config/mise/…, conf.d fragments, .tool-versions, and their local, env-specific and .lock variants. The step also logs Hashed mise config files in N.Ns. (#703 by @​jdx and @​corsicanec82)
    • If you set a custom cache_key that doesn't use {{file_hash}} or {{default}}, the action no longer hashes config files at all.
    • Config files in subdirectories, such as monorepo sub-projects, no longer affect the cache key. mise only loads them with --monorepo.
    • Cache keys change, so the first run after you upgrade will miss the cache.

New Contributors

Full Changelog: jdx/mise-action@v5.2.2...v5.2.3

v5.2.2: Include conf.d config fragments in the cache key

The cache key now includes mise conf.d/*.toml config fragments, so changing one of them invalidates the cache.

Fixed

  • Editing a conf.d fragment now invalidates the cache. mise can load config from single-file fragments in conf.d/ directories, but the action didn't hash those files when it built the cache key. As a result, adding or changing tools in a fragment could restore an outdated cache. The cache key now also hashes conf.d/*.toml files under .config/mise/, .mise/ and mise/. If your repo already uses these fragments, the cache will miss once after you upgrade. (#698 by @​rileymichael)

New Contributors

Full Changelog: jdx/mise-action@v5.2.1...v5.2.2

v5.2.1: Require the signed packslip for mise 2026.9.3 and later

The action now refuses to install mise 2026.9.3 or later if the release's signed packslip is missing. This closes a gap where verification could be downgraded to the weaker checksum check.

Fixed

  • A missing packslip no longer weakens the check on recent mise releases. v5.2.0 started checking the mise binary against the release's signed packslip.sigstore.json. If that file wasn't found, though, the action quietly fell back to the minisign-signed SHASUMS256 checksums. Anyone who could hide the file could force the weaker check. Every mise release from 2026.9.3 on includes a packslip, so for those versions a missing bundle now stops the install with an error like this: 
    mise v2026.10.11 must ship a signed packslip, but https://github.com/jdx/mise/releases/download/v2026.10.11/packslip.sigstore.json was not found
    Releases before 2026.9.3 don't include a packslip, so they're still checked against the signed checksums. A version string that isn't three dot-separated numbers also requires a packslip. If you set the sha256 input, it still takes precedence over both checks. A packslip that fails verification still never falls back to the checksums. (#695 by @​jdx)

... (truncated)

Changelog

Sourced from jdx/mise-action's changelog.

Changelog

5.2.5 - 2026-10-30

🔍 Other Changes

5.2.4 - 2026-10-27

🐛 Bug Fixes

  • (cache) reuse signed checksums saved with a cached mise (#708) by @​jdx in #708

5.2.3 - 2026-10-24

🐛 Bug Fixes

  • (cache) hash mise config files without walking the workspace (#703) by @​jdx in #703

5.2.2 - 2026-10-21

🐛 Bug Fixes

New Contributors

5.2.1 - 2026-10-19

🐛 Bug Fixes

  • require the signed packslip for mise 2026.9.3 and later (#695) by @​jdx in #695

5.2.0 - 2026-10-16

🚀 Features

  • (cache) rebuild the cache every 30 days by default (#689) by @​jdx in #689
  • (cache) retry throttled cache restores and saves (#692) by @​jdx in #692
  • verify the mise binary against its signed packslip (#693) by @​jdx in #693

... (truncated)

Commits

Updates nais/deploy/actions/deploy from fa754451577294aae42872a69b888b3470478ec1 to 3944168fd20b7eea3818e97de3810f74b54c78ff

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

@dependabot
chore(deps): bump the github-actions group across 1 directory with 5 …
0b40517 
…updates

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

| Package | From | To |
| --- | --- | --- |
| [github/codeql-action/init](https://github.com/github/codeql-action) | `4.38.3` | `4.39.1` |
| [actions/setup-java](https://github.com/actions/setup-java) | `6.0.1` | `6.1.0` |
| [github/codeql-action/analyze](https://github.com/github/codeql-action) | `4.38.3` | `4.39.1` |
| [jdx/mise-action](https://github.com/jdx/mise-action) | `5.1.2` | `5.2.4` |
| [nais/deploy/actions/deploy](https://github.com/nais/deploy) | `fa754451577294aae42872a69b888b3470478ec1` | `3944168fd20b7eea3818e97de3810f74b54c78ff` |



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 `actions/setup-java` from 6.0.1 to 6.1.0
- [Release notes](https://github.com/actions/setup-java/releases)
- [Commits](actions/setup-java@de7274f...b843ebf)

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 `jdx/mise-action` from 5.1.2 to 5.2.4
- [Release notes](https://github.com/jdx/mise-action/releases)
- [Changelog](https://github.com/jdx/mise-action/blob/main/CHANGELOG.md)
- [Commits](jdx/mise-action@08ae2a0...6be3c7e)

Updates `nais/deploy/actions/deploy` from fa754451577294aae42872a69b888b3470478ec1 to 3944168fd20b7eea3818e97de3810f74b54c78ff
- [Release notes](https://github.com/nais/deploy/releases)
- [Commits](nais/deploy@fa75445...3944168)

---
updated-dependencies:
- dependency-name: github/codeql-action/init
  dependency-version: 4.39.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: actions/setup-java
  dependency-version: 6.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: github/codeql-action/analyze
  dependency-version: 4.39.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: jdx/mise-action
  dependency-version: 5.2.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: nais/deploy/actions/deploy
  dependency-version: 3944168fd20b7eea3818e97de3810f74b54c78ff
  dependency-type: direct:production
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants