Upgrade CodeQL caching and dependencies installation - #1186
Open
mbaluda wants to merge 12 commits into
Open
Conversation
Updated CodeQL workflow to use caching
Updated caching strategy for CodeQL to use a new path and key format.
mbaluda
marked this pull request as ready for review
August 27, 2026 13:33
mbaluda
requested review from
MichaelRFairhurst
and
a balanced review from Copilot
August 27, 2026 13:33
Contributor
There was a problem hiding this comment.
Pull request overview
Adds persistent CodeQL compilation caching to accelerate unit tests and pack generation. A change note is not required because query behavior and release artifacts are unchanged.
Changes:
- Restores and saves versioned compilation caches.
- Shares caches across dependency installation, compilation, testing, and bundling.
- Updates unit-test caching to
actions/cache@v6.
Show a summary per file
| File | Description |
|---|---|
scripts/install-packs.py |
Adds common-cache support to pack installation. |
.github/actions/install-codeql-packs/action.yml |
Exposes the cache directory input. |
.github/workflows/codeql_unit_tests.yml |
Caches compiled queries for unit tests. |
.github/workflows/code-scanning-pack-gen.yml |
Caches compilation and bundle generation. |
Review details
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 4/4 changed files
- Comments generated: 0
- Review effort level: Balanced
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 pull request enhances the unit_tests and pack-gen workflows by introducing a persistent cache for compiled queries.
Description
It updates the related GitHub Actions and scripts to support the new caching mechanism.
Performance Improvement
When the cache is fully warm (no query needs to be recompiled), performance is improved by ~90%
Change request type
.ql,.qll,.qlsor unit tests)Rules with added or modified queries
Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:
If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?
🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.
Reviewer: Confirm that either a change note is not required or the change note is required and has been added.
Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
Reviewer
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.