chore: bump pinned CodeQL CLI to v2.26.3 - #223
Merged
Merged
Conversation
Contributor
Dang it |
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.
Automated CLI version bump, requested via the "Update CodeQL CLI Version"
workflow (
workflow_dispatch,codeql_version: 2.26.3,release_bump: (none)).This PR:
.codeqlversionto2.26.3.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.
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.This PR does not publish anything by itself - no pack
version:field isbumped here, so
publish.yml's version-diff trigger won't fire for it yet.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.
(
update-release.yml) to bump every pack'sversion:in lockstep via.release.ymland trigger the real batch publish.