ci(deps): Bump the actions group with 3 updates

[dependabot]

Bumps the actions group with 3 updates: actions/setup-java, github/codeql-action/init and github/codeql-action/analyze.

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

• Preserve compound Liberica build versions from .sdkmanrc by @​brunoborges with @​Copilot in actions/setup-java#1268
• Support Temurin on Linux RISC-V by @​yawkat in actions/setup-java#1269
• Stop GPG agent before removing signature-verification home by @​brunoborges with @​Copilot in actions/setup-java#1273
• Prefer Zulu 4-segment hotfix builds when resolving version ranges by @​brunoborges in actions/setup-java#1278
• Support Temurin JEP 322 patch versions like 26.0.2.1+1 by @​brunoborges in actions/setup-java#1279
• chore(deps): bump undici from 6.28.0 to 6.29.0 by @​dependabot[bot] in actions/setup-java#1274
• chore(deps): bump the monthly-npm-updates group with 13 updates by @​dependabot[bot] in actions/setup-java#1276
• feat: support Maven server credential origins by @​YunaBraska in actions/setup-java#1282
• Support Maven plugin repositories in generated settings.xml by @​brunoborges in actions/setup-java#1286

New Contributors

• @​yawkat made their first contribution in actions/setup-java#1269
• @​YunaBraska made their first contribution in actions/setup-java#1282

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/init from 4.38.3 to 4.39.0

Release notes

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

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

• 6f2ac81 Merge pull request #4239 from github/update-v4.39.0-d63383a73
• eb1c428 Trigger workflows
• 4443333 Update changelog for v4.39.0
• d63383a Merge pull request #4233 from github/mbg/start-proxy/report-version
• 8dec0b9 Rename path to result in tests
• 4eabea6 Merge remote-tracking branch 'origin/main' into mbg/start-proxy/report-version
• 57938b8 Merge pull request #4201 from github/mario-campos/automate-changenotes-assemble
• ee07b50 Merge pull request #4236 from github/mbg/add-missing-changenotes
• a897ed5 Add change note for #4206
• c8bd019 Add change note for #4198
• Additional commits viewable in compare view

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

Release notes

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

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

• 6f2ac81 Merge pull request #4239 from github/update-v4.39.0-d63383a73
• eb1c428 Trigger workflows
• 4443333 Update changelog for v4.39.0
• d63383a Merge pull request #4233 from github/mbg/start-proxy/report-version
• 8dec0b9 Rename path to result in tests
• 4eabea6 Merge remote-tracking branch 'origin/main' into mbg/start-proxy/report-version
• 57938b8 Merge pull request #4201 from github/mario-campos/automate-changenotes-assemble
• ee07b50 Merge pull request #4236 from github/mbg/add-missing-changenotes
• a897ed5 Add change note for #4206
• c8bd019 Add change note for #4198
• 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

[MRegra]

fleet review

reviewer: PASS

PR #18 is an automated Dependabot "actions" group bump touching only .github/workflows/ci.yml and security.yml (2 files, 3 lines changed): actions/setup-java pinned-SHA 6.0.1→6.1.0, and github/codeql-action/init + analyze pinned-SHA 4.38.3→4.39.0. Each new SHA in the diff matches the SHA Dependabot cites in the PR body for the stated version tag, so no SHA/tag mismatch. No functional code changes, no manifests, no migrations, no secrets touched — this is pure CI tooling maintenance, not a fix for an application defect, so "root cause" and "regression test" don't apply in the usual sense; the applicable acceptance bar is "keeps CI actions current without breaking the pipeline," which it meets.

CI: ran gh pr checks 18 — all 5 checks green (CodeQL, CodeQL (java), Dependency review, Secrets scan, build), confirming the bumped setup-java and codeql-action versions work in this repo's actual workflows. No Maven/npm tests apply since no app code changed; I did not run mvn -f backend/pom.xml test since nothing under backend/ changed.

Safe to deploy: this is a repo env GitOps-irrelevant change (workflow files only, no runtime deploy artifact), reversible by reverting the PR, no backwards-compatibility or secret-handling concerns. CodeQL 4.39.0 has a noted breaking change (min CodeQL bundle version 2.20.7) but the green CI run proves this repo isn't affected.

Minimal and in scope: yes, exactly the 3 Dependabot-grouped bumps, nothing unrelated.

attempted

• git diff origin/main...HEAD
• gh pr checks 18 -R MRegra/tuplo
• gh pr view 18 -R MRegra/tuplo --json title,body,additions,deletions,changedFiles,files

adversary: PASS

I couldn't break this Dependabot bump. The PR changes three pins: actions/setup-java goes from v6.0.1 to v6.1.0, and github/codeql-action init and analyze go from v4.38.3 to v4.39.0. All three stay pinned by a full 40-character commit SHA with a version comment, so no mutable tag is introduced. Nothing else changes: workflow permissions (permissions: {} at the top of security.yml, a narrow set per job, contents: read in ci.yml), triggers, inputs and persist-credentials: false are all the same. A grep shows no leftover references to the old SHAs or versions in any workflow or doc, so the update is complete. Within each major version (v6, v4) the inputs we use (distribution, java-version, cache; languages, build-mode, category) are still standard. Reverting the merge only restores the previous SHA pins, so rollback is safe, and nothing is deployed from this change. One thing I could not check: whether the new SHAs actually match the upstream v6.1.0 and v4.39.0 tags. git ls-remote and WebFetch were both denied (no network), so the reviewer should confirm this, and that CI on this PR is green, which shows the pinned commits resolve and run.

attempted

• git diff origin/main...HEAD: only the 3 uses: SHA pins changed, in ci.yml and security.yml
• Grep for every uses: under .github: every action is still pinned by a full SHA, and no other workflow uses the old setup-java or codeql-action SHAs
• Grep for the old SHAs, 'v6.0.1', 'v4.38.3', 'setup-java', 'codeql-action' across the repo: no stale references left
• Read both workflows in full: permissions, triggers, concurrency, persist-credentials and action inputs are unchanged and still valid for the same major version
• Rollback: a revert only restores the previous SHA pins; nothing is deployed, no migrations, no runtime impact
• Tried git ls-remote and a web-fetch subagent to check the new SHAs against the upstream tags: both denied (no network), so the check is left to the reviewer and CI

security: PASS

PR #18 is a Dependabot change (author app/dependabot) that moves three GitHub Actions pins forward and touches nothing else. actions/setup-java goes from v6.0.1 (de7274f) to v6.1.0 (b843ebf). github/codeql-action/init and /analyze both go from v4.38.3 (24c5418) to v4.39.0 (6f2ac81). Each action is still pinned to a full 40-character commit SHA with a version comment. Workflow permissions, triggers, persist-credentials:false, the gitleaks/CodeQL/dependency-review gates and the Maven verify step are all unchanged. There is no pull_request_target and no new secrets or permissions. Both new SHAs are the release-tip commits in the upstream compare views that Dependabot linked (de7274f...b843ebf and 24c5418...6f2ac81). All 5 PR checks pass on the new pins: build, CodeQL (java), Secrets scan (gitleaks), Dependency review and CodeQL. That green CodeQL run shows the 4.39.0 init/analyze actually ran and is not silently skipped. The breaking change in 4.39.0 (minimum CodeQL bundle 2.20.7) does not affect this repo because it uses the default bundle. The new setup-java features (Maven server credential origins, plugin repositories in the generated settings.xml) are not used here: no server-id or credential inputs are set. Nothing here is exploitable and no gate is weakened.

• nit Tag→SHA mapping not re-checked against the upstream refs API (.github/workflows/ci.yml, .github/workflows/security.yml)
  I could not run gh api repos/<owner>/<repo>/git/ref/tags/<tag> or git ls-remote because shell permissions were denied. So I could not confirm independently that v6.1.0 resolves to b843ebf and v4.39.0 to 6f2ac81. What I did confirm: Dependabot authored the PR, the SHAs appear as the tip commits in the actions/setup-java and github/codeql-action compare views the PR links to, and CI ran green with them. This doesn't block the PR. A reviewer with API access could run that tag lookup to close out impostor-commit risk completely.
  proof

gh pr view 18 --json author → app/dependabot; PR body commit lists: actions/setup-java/commit/b843ebf9b913146b38da2eaa7aeddf76074ae1ad (#1286, tip of v6.0.1...v6.1.0) and github/codeql-action/commit/6f2ac81f5cd81fe351a197ba0b00d91d03cd2aee (Merge #4239 update-v4.39.0); statusCheckRollup: build, CodeQL (java), Secrets scan (gitleaks), Dependency review, CodeQL all SUCCESS.

attempted

• git diff origin/main...HEAD: 3 lines changed, pin bumps only, in ci.yml and security.yml
• Read both workflows: permissions {} at top level with per-job least privilege (security-events: write only on the CodeQL job), contents: read on CI, persist-credentials: false on every checkout, no pull_request_target
• gh pr view 18: Dependabot author, release notes and compare views read for breaking changes
• gh pr view statusCheckRollup: all 5 checks SUCCESS on the new pins
• Tried gh api / git ls-remote to resolve the tags to SHAs: permission denied

Approvals: 3/3 on 422c14e

🤖 Generated with Claude Code