Skip to content

Upgrade CodeQL CLI dependency to v2.25.0#161

Open
github-actions[bot] wants to merge 5 commits intomainfrom
codeql/upgrade-to-v2.25.0
Open

Upgrade CodeQL CLI dependency to v2.25.0#161
github-actions[bot] wants to merge 5 commits intomainfrom
codeql/upgrade-to-v2.25.0

Conversation

@github-actions
Copy link
Contributor

This PR upgrades the CodeQL CLI version to v2.25.0.

Changes made:

  • Updated .codeql-version to v2.25.0
  • Updated all version-bearing files (package.json, extensions/vscode/package.json, codeql-pack.yml) to 2.25.0
  • Regenerated package-lock.json
  • Upgraded CodeQL pack lock files
  • Build and tests passed ✅

@github-actions github-actions bot force-pushed the codeql/upgrade-to-v2.25.0 branch from a5a6b3e to 85c6885 Compare March 23, 2026 18:26
@github-actions github-actions bot requested review from a team, data-douser and enyil as code owners March 23, 2026 18:26

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trying to track down the license for this, I think this might be an internal project vscode-codeql-development-mcp-server or similar but not third party. Can you confirm?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. It is equivalent to the extensions/vscode workspace (aka extensions/vscode/package.json:name = vscode-codeql-development-mcp-server) in this repo.

I don't know how to get the license compliance check to recognize the peer dependency in the multi-workspace setup.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dangoor any suggestions on the formatting for this internal dependency? I can accept it as it is into the current policy if desired (though this could lead to dependency confusion in the future), but we might want to dig into this to give guidance in general....

@data-douser data-douser reopened this Mar 23, 2026
@github-actions
Copy link
Contributor Author

github-actions bot commented Mar 23, 2026

Dependency Review

The following issues were found:
  • ✅ 0 vulnerable package(s)
  • ✅ 0 package(s) with incompatible licenses
  • ✅ 0 package(s) with invalid SPDX license definitions
  • ⚠️ 3 package(s) with unknown licenses.
See the Details below.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA d9eb58a.
Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

License Issues

package-lock.json

PackageVersionLicenseIssue Type
client2.25.0NullUnknown License
extensions/vscode2.25.0NullUnknown License
server2.25.0NullUnknown License

OpenSSF Scorecard

PackageVersionScoreDetails
npm/client 2.25.0 UnknownUnknown
npm/extensions/vscode 2.25.0 UnknownUnknown
npm/server 2.25.0 UnknownUnknown

Scanned Files

  • package-lock.json

data-douser and others added 3 commits March 23, 2026 18:29
Fixes "tools" queries in response to breaking changes
from recent upgrade to CodeQL v2.25.0 and associated
pack dependency upgrades, including fixes for:

- `server/ql/go/tools/{src,test}/PrintAST/**`
- `server/ql/java/tools/{src,test}/PrintCFG/**`

Updates language-specific AST resource definitions in
order to reflect actual AST nodes for current (v2.25.0)
version of CodeQL and associated pack dependencies,
including updates for MCP resources:

- `go_ast`
- `java_ast`
@data-douser data-douser force-pushed the codeql/upgrade-to-v2.25.0 branch from 90f04db to b1dff3e Compare March 24, 2026 00:31
Update the query implementation, documentation, and expected test
results for the java tools PrintAST query in order to fix a problem
where Entry nodes were non-deterministically ordered, especially
between MacOS and Linux test environments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants