Pull Request Overview
- Opened on October 19, 2026
- Status Merged
- Commit count 1 with first commit October 19, 2026
Total Delta
Open Days
Test Delta
How long has this pull request spent in each phase of its lifecycle?
| Fraction of total time | Business days | Phase |
|---|---|---|
|
|
0.0 days | Authoring 1 commit before pull request opened for review |
|
|
0.4 days | Awaiting first review |
| Set up deploy tracking to begin tracking full PR start-to-deploy times | ||
Total time for pull request
0.4 business days
from first commit authored to merge
Deploy tracking has not been set up
chore(deps): bump github/codeql-action from 4.38.2 to 4.39.0
Bumps github/codeql-action from 4.38.2 to 4.39.0.
Release notes
Sourced from github/codeql-action's releases.
v4.39.0
Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205- The
codeql-action/analyzestep now validates that a correct argument for thecheckout_pathinput has been provided. Thecheckout_pathinput 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 bycodeql-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-proxystep that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic ascodeql-action/init. This primarily benefits customers who are using GitHub instances other thangithub.comwhere thecodeql-action/start-proxystep may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198v4.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's changelog.
4.39.0 - 15 Oct 2026
Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205- The
codeql-action/analyzestep now validates that a correct argument for thecheckout_pathinput has been provided. Thecheckout_pathinput 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 bycodeql-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-proxystep that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic ascodeql-action/init. This primarily benefits customers who are using GitHub instances other thangithub.comwhere thecodeql-action/start-proxystep may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #41984.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
Commits
-
6f2ac81Merge pull request #4239 from github/update-v4.39.0-d63383a73 -
eb1c428Trigger workflows -
4443333Update changelog for v4.39.0 -
d63383aMerge pull request #4233 from github/mbg/start-proxy/report-version -
8dec0b9Renamepathtoresultin tests -
4eabea6Merge remote-tracking branch 'origin/main' into mbg/start-proxy/report-version -
57938b8Merge pull request #4201 from github/mario-campos/automate-changenotes-assemble -
ee07b50Merge pull request #4236 from github/mbg/add-missing-changenotes -
a897ed5Add change note for #4206 -
c8bd019Add 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 ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Comments Threads Pending Resolution
Resolved Comment Threads
No resolved comments have been left on this PR.