[dependabot]

Bumps github/codeql-action/autobuild from 4.39.0 to 4.39.1.

Release notes

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

v4.39.1

• Update default CodeQL bundle version to 2.27.3. #4256

Changelog

Sourced from github/codeql-action/autobuild'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

[mergify]

Merge Protections

🟢 All 3 merge protections satisfied — ready to merge.

Show 3 satisfied protections

🟢 Full CI must pass

All CI checks must pass. This protection prevents manual merges that bypass the merge queue.

• check-success = coverage
• check-success = msrv (stable minus 1 releases)
• check-success = msrv (stable minus 2 releases)
• check-success = msrv (stable minus 3 releases)
• check-success = msrv (stable minus 4 releases)
• check-success = msrv (stable)
• check-success = quality
• check-success = test
• check-success = test-cross-platform (macos-latest, macOS)
• check-success = test-cross-platform (ubuntu-latest, Linux)
• check-success = test-cross-platform (windows-latest, Windows)

🟢 Do not merge outdated PRs

Make sure PRs are within 10 commits of the base branch before merging

• #commits-behind <= 10

🟢 🚦 Auto-queue

When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.

• any of:
  • all of:
    • author = dependabot[bot]
    • base = main
  • all of:
    • author = dosubot[bot]
    • base = main

[mergify]

Automatically approved by Mergify

[mergify]

🚫 Left the queue

33 min in the queue, with no time running CI.

So far

• ✅ Entered the queue Wed 28 Oct, 07:35 · rule dependabot · triggered by merge protections
• ⏹️ Testing stopped · draft merge queue: checking #409 on main (7280a6f), stacked on #405, #408 and #407 #413
• 🚫 Left the queue 08:08 · 55e94db

Reason

The pull request #409 has been manually updated

Requeued — the merge queue status continues in this comment ↓.

_{Times in UTC · dashboard · how the merge queue works}

[mergify]

✅ Merged into main as 011ecd1 at 09:21 UTC

37 min in the queue, 36 min of it CI.

So far

• ✅ Entered the queue Wed 28 Oct, 08:44 · rule dependabot · triggered by merge protections
• ✅ Passed · draft merge queue: checking #409 on main (6c1ea1a) #415
• ✅ Merged 09:21 · 011ecd1 · squash

Merge conditions: 15 of 15 met

This pull request

	Condition	Required by
✅	github-code-owner-review-satisfied	GitHub repository ruleset rule main
✅	github-review-approved	GitHub repository ruleset rule main and GitHub repository ruleset rule ossf_best_practices
✅	#commits-behind <= 10	Merge Protections rule Do not merge outdated PRs

The batch, tested on draft #415

	Condition	Required by
✅	check-success = coverage	Merge Protections rule Full CI must pass
✅	check-success = msrv (stable minus 1 releases)	Merge Protections rule Full CI must pass
✅	check-success = msrv (stable minus 2 releases)	Merge Protections rule Full CI must pass
✅	check-success = msrv (stable minus 3 releases)	Merge Protections rule Full CI must pass
✅	check-success = msrv (stable minus 4 releases)	Merge Protections rule Full CI must pass
✅	check-success = msrv (stable)	Merge Protections rule Full CI must pass
✅	check-success = quality	Merge Protections rule Full CI must pass
✅	check-success = test	Merge Protections rule Full CI must pass
✅	check-success = test-cross-platform (macos-latest, macOS)	Merge Protections rule Full CI must pass
✅	check-success = test-cross-platform (ubuntu-latest, Linux)	Merge Protections rule Full CI must pass
✅	check-success = test-cross-platform (windows-latest, Windows)	Merge Protections rule Full CI must pass
✅	any of: check-neutral = @mergify/Mergify Merge Protections, check-skipped = @mergify/Mergify Merge Protections, check-success = @mergify/Mergify Merge Protections	GitHub repository ruleset rule main

_{Times in UTC · dashboard · how the merge queue works}