Repository navigation
chore: bump pinned CodeQL CLI to v2.27.3 and release v0.8.3 - #238
Conversation
|
@copilot any explanation for this out of disk, this is new with this change? |
The failure is during Hotspots query generation: CodeQL reports |
Co-authored-by: felickz <1760475+felickz@users.noreply.github.com>
Co-authored-by: felickz <1760475+felickz@users.noreply.github.com>
…d on #238) (#240) * chore: bump pinned CodeQL CLI to v2.27.3 and release v0.8.3 * Add Hotspots query resource diagnostics Co-authored-by: felickz <1760475+felickz@users.noreply.github.com> * Cap Hotspots evaluator disk cache Co-authored-by: felickz <1760475+felickz@users.noreply.github.com> * fix(hotspots): avoid cartesian product when resolving config import strings getImportStringFrom compared the config file's dotted path against Import.getImportString() with matches("%" + importString). That non-equality string join gives the optimizer nothing to bind on, and with CodeQL 2.27.3 (github/codeql codeql-cli/v2.27.3) it planned a cartesian product of ~33k import tuples with the 15M-row locations_default relation, filling the runner disk. Materialize the config's dotted-path suffixes in a pragma[nomagic] helper and join on string equality instead. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * ci(hotspots): TEMPORARY run Hotspots CI on PRs stacked on CLI bump branches hotspots-ci.yml only triggers for PRs targeting main, so a PR stacked on chore/update-codeql-cli-* would get no hotspots signal. Drop this commit before merging the fix into the bump branch. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Automated CLI version bump, requested via the "Update CodeQL CLI Version"
workflow (
workflow_dispatch,codeql_version: 2.27.3,release_bump: patch).This PR:
Updates
.codeqlversionto2.27.3.Pins every
codeql/<lang>-all/codeql/<lang>-queriesdependencies:entry across query/library
qlpack.ymlfiles (not*/extor*/ext-library-sources, whoseextensionTargetsis intentionally leftunconstrained and must never be auto-rewritten) to the exact version
shipped in the official CodeQL Bundle for this CLI release (see
.github/scripts/pin-codeql-library-versions.sh) - this keepscodeql pack upgradefrom jumping those libraries to registry-latest insteadof the version this CLI actually ships/tests against.
Runs
codeql pack upgrade <dir>for every query/library pack directory (againexcluding
*/extand*/ext-library-sources) to refresh itscodeql-pack.lock.ymlagainst the new CLI and pinned library versions.Also bumps the repo release version (
patch, via the samepatch-release-mestepupdate-release.ymluses) to0.8.3,propagating it to every pack's own
version:field,configs/*.ymlreferences, and cross-pack
-libspins.Merging this PR triggers the real batch publish -
publish.yml'sauto-trigger fires on any push to
mainthat changes.release.yml, which thisPR does. No separate "CodeQL Update Release" run is needed. That run's
summaryjob will create the matching GitHub Release as a full release
(
release_prerelease: false).Remaining steps (see CONTRIBUTING.md's "Updating the pinned CodeQL CLI/library
version" section):
API changes. This is usually the hardest part; consider delegating it to a
Copilot coding agent session pointed at this PR/branch.