chore: bump all pack versions to 0.5.1#182
Merged
Merged
Conversation
.release.yml and the v0.5.1 GitHub Release were already cut (via update-release.yml), but no pack's own qlpack.yml version was bumped to match, so publish.yml's diff check (local qlpack.yml version vs published GHCR tag) found nothing to publish and the release notes were never actually shipped as packages. Bump every language's src/lib/ext/ext-library-sources qlpack.yml version from 0.5.0 to 0.5.1 (matching the already-declared release version, since nothing was ever actually published under that tag) so a follow-up publish.yml run ships the real packages. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR aligns all CodeQL Community Pack qlpack.yml versions with the already-cut v0.5.1 release by bumping pack versions from 0.5.0 to 0.5.1, enabling publish.yml to actually publish the packs.
Changes:
- Bump Ruby pack versions (
src,lib) to0.5.1. - Bump Python/Java/Go/C# pack versions (
src,lib,ext,ext-library-sourceswhere applicable) to0.5.1. - Bump JavaScript and C++ pack versions (
src,lib) to0.5.1.
Show a summary per file
| File | Description |
|---|---|
| ruby/src/qlpack.yml | Bump Ruby queries pack version to 0.5.1. |
| ruby/lib/qlpack.yml | Bump Ruby libs pack version to 0.5.1. |
| python/src/qlpack.yml | Bump Python queries pack version to 0.5.1. |
| python/lib/qlpack.yml | Bump Python libs pack version to 0.5.1. |
| python/ext/qlpack.yml | Bump Python extensions pack version to 0.5.1. |
| javascript/src/qlpack.yml | Bump JavaScript queries pack version to 0.5.1. |
| javascript/lib/qlpack.yml | Bump JavaScript libs pack version to 0.5.1. |
| java/src/qlpack.yml | Bump Java queries pack version to 0.5.1. |
| java/lib/qlpack.yml | Bump Java libs pack version to 0.5.1. |
| java/ext/qlpack.yml | Bump Java extensions pack version to 0.5.1. |
| java/ext-library-sources/qlpack.yml | Bump Java library-sources pack version to 0.5.1. |
| go/src/qlpack.yml | Bump Go queries pack version to 0.5.1. |
| go/lib/qlpack.yml | Bump Go libs pack version to 0.5.1. |
| go/ext/qlpack.yml | Bump Go extensions pack version to 0.5.1. |
| csharp/src/qlpack.yml | Bump C# queries pack version to 0.5.1. |
| csharp/lib/qlpack.yml | Bump C# libs pack version to 0.5.1. |
| csharp/ext/qlpack.yml | Bump C# extensions pack version to 0.5.1. |
| csharp/ext-library-sources/qlpack.yml | Bump C# library-sources pack version to 0.5.1. |
| cpp/src/qlpack.yml | Bump C++ queries pack version to 0.5.1. |
| cpp/lib/qlpack.yml | Bump C++ libs pack version to 0.5.1. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 20/20 changed files
- Comments generated: 0
- Review effort level: Low
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.
What
Bumps every language's
src/lib/ext/ext-library-sourcesqlpack.ymlversion:field from0.5.0→0.5.1(20 files,ql/hotspots/and*/test/excluded, matching.release.yml's own excludes).Why
.release.ymlwas already bumped to0.5.1and thev0.5.1GitHub Release was already cut (viaupdate-release.yml/PR #180), but no pack's ownqlpack.ymlversion was bumped to match.publish.ymlonly publishes a pack when its localqlpack.ymlversion differs from what's currently on GHCR — since every pack was still at0.5.0locally, a manualworkflow_dispatchofpublish.ymlcorrectly found nothing to publish. Thev0.5.1release notes/changelog exist, but no package was ever actually shipped under that version.Staying at
0.5.1(rather than skipping to0.5.2) since nothing was ever actually published as0.5.1— this just makes the real packages catch up to the release that's already been cut.Follow-up (separate, not blocking this PR)
.release.yml's custom"CodeQL Packs"location is supposed to auto-bump everyqlpack.yml's version viapatch-release-mewhenever.release.ymlitself is bumped, but it silently didn't fire for this release (it did work for the prior0.4.0→0.5.0cut). Will investigate why as a separate follow-up so this manual catch-up step isn't needed on every future release.Next step after merge
Manually dispatch
publish.yml(workflow_dispatch) to actually publish all packs at0.5.1.Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com