Overlay: Increase minimum CLI version required for overlay analysis#3317
Merged
Overlay: Increase minimum CLI version required for overlay analysis#3317
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR increases the minimum CodeQL CLI version required for overlay analysis from 2.22.4 to 2.23.5, which is the current release version. The change ensures that overlay analysis features will only be enabled when users have a CLI version that supports all the latest overlay functionality.
- Updated the
CODEQL_OVERLAY_MINIMUM_VERSIONconstant in the TypeScript source - All generated JavaScript files automatically reflect this change
Reviewed Changes
Copilot reviewed 13 out of 13 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| src/overlay-database-utils.ts | Updates the minimum CLI version constant for overlay analysis from 2.22.4 to 2.23.5 |
| lib/upload-sarif-action.js | Generated JavaScript reflecting the TypeScript change |
| lib/upload-sarif-action-post.js | Generated JavaScript reflecting the TypeScript change |
| lib/upload-lib.js | Generated JavaScript reflecting the TypeScript change |
| lib/start-proxy-action.js | Generated JavaScript reflecting the TypeScript change |
| lib/start-proxy-action-post.js | Generated JavaScript reflecting the TypeScript change |
| lib/setup-codeql-action.js | Generated JavaScript reflecting the TypeScript change |
| lib/resolve-environment-action.js | Generated JavaScript reflecting the TypeScript change |
| lib/init-action.js | Generated JavaScript reflecting the TypeScript change |
| lib/init-action-post.js | Generated JavaScript reflecting the TypeScript change |
| lib/autobuild-action.js | Generated JavaScript reflecting the TypeScript change |
| lib/analyze-action.js | Generated JavaScript reflecting the TypeScript change |
| lib/analyze-action-post.js | Generated JavaScript reflecting the TypeScript change |
mbg
approved these changes
Nov 19, 2025
This was referenced Nov 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR bumps the minimum CLI version required for overlay analysis to v. 2.23.5 (current release). This isn't strictly necessary, but simplifies operations by reducing the number of CLI versions we have to consider.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
dynamicworkflows (Default Setup, CCR, ...).Products:
analysis-kinds: code-scanning.analysis-kinds: code-quality.Environments:
github.com.How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
Overlay analysis is currently feature flagged.
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist