Skip to content

Add python and go extension to publish workflow - #144

Merged
felickz merged 8 commits into
GitHubSecurityLab:mainfrom
Hug0Vincent:patch-1
Jul 27, 2026
Merged

Add python and go extension to publish workflow#144
felickz merged 8 commits into
GitHubSecurityLab:mainfrom
Hug0Vincent:patch-1

Conversation

@Hug0Vincent

Copy link
Copy Markdown
Contributor

Add python and go extension to publish workflow

Add python and go extension to publish workflow
@Hug0Vincent Hug0Vincent mentioned this pull request Mar 25, 2026
felickz added a commit that referenced this pull request Jul 6, 2026
- pr-version-bump-check.sh: only check ext/ext-library-sources for
  csharp/java, matching publish.yml's actual matrix. go/ext and
  python/ext exist but aren't published by publish.yml (see #144), so
  telling contributors a version bump would ship them was misleading.
- check-codeql-release.sh: replace broken `../blob/main/...` relative
  links in the generated issue body with full https://github.com/...
  URLs (derived from $GITHUB_REPOSITORY), since GitHub issue markdown
  resolves relative links against the issue's own path, not the repo
  root.
- ci.yml: rename the advisory job from "Check pack version was bumped"
  to "Warn if pack version bump is missing" so the Actions UI doesn't
  imply the version was actually bumped when this job runs/passes.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
felickz added a commit that referenced this pull request Jul 10, 2026
.release.yml's version was bumped to 0.2.3 directly (not via a pack
version bump), and java/lib was independently bumped to 0.2.3 by
PR #155's hotfix. This closes the gap by bringing every other pack's
own qlpack.yml version in line, so merging this triggers the real
batch publish of everything to 0.2.3 (java/lib is already live and
will be a no-op).

Also bumps go/ext and python/ext/qlpack.yml for consistency with
.release.yml's 'CodeQL Pack Versions' location pattern, even though
those two packs aren't wired into publish.yml's matrix yet (tracked
by open PR #144).

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Expands the publish workflow’s extensions job matrix so that CodeQL extension packs for additional languages are published alongside the existing ones.

Changes:

  • Add python and go to the extensions job language matrix in .github/workflows/publish.yml.
Show a summary per file
File Description
.github/workflows/publish.yml Extends the extensions job matrix to include python and go so their extension packs can be published.

Review details

  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Low

Comment thread .github/workflows/publish.yml Outdated
felickz

This comment was marked as outdated.

@felickz felickz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Verified this against main

What I checked:

  • python/ext/qlpack.yml and go/ext/qlpack.yml already exist on main (added back in the 0.2.0 era) and have been kept version-bumped in lockstep with csharp/java through every release since (currently 0.7.0). They're already part of the release process — they've just never actually been published, because this extensions job matrix excludes them.
  • Confirmed on GHCR: codeql-java-extensions is live at 0.7.0, but codeql-python-extensions and codeql-go-extensions both 404 — i.e. this gap is real and exactly matches what this PR fixes.
  • Locally ran codeql pack install + codeql pack create (CLI 2.25.6, same as CI) against python/ext and go/ext — both succeed (exit 0, "Library pack creation complete"), with only the same pre-existing addsTo.pack ... is not an extension target warning that also fires today for the already-published csharp/ext and java/ext. So that warning is a repo-wide, pre-existing cosmetic issue, not something this change introduces or something blocking a first publish.
  • This job has no csharp/java-specific logic outside the matrix (${{ matrix.language }}/ext is used throughout, and the "package doesn't exist yet" 404 case is already handled via || true), so a first-time publish for python/go will behave the same way csharp/java's did originally.

*Two small changes

  1. .github/workflows/ci.yml has a sibling extensions job (matrix at line ~168) that's also hardcoded to ["csharp", "java"] and validates pack install/pack create on every PR touching <lang>/ext/**. It's not touched by this PR, so python/ext/go/ext changes still won't get CI coverage even after this merges. Worth adding python/go there too for parity:
    -        language: [ 'csharp', 'java' ]
    +        language: [ 'csharp', 'java', 'python', 'go' ]
    
  2. CONTRIBUTING.md currently has a line that explicitly calls out this PR by number ("ext/ext-library-sources only run for csharp/java today, see #144") — that caveat should be removed/updated

felickz and others added 5 commits July 27, 2026 16:26
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Updated the supported languages for extensions in the contributing guidelines.

@felickz felickz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

:octocat: 👍

Thanks for the contribution @Hug0Vincent !!

@felickz
felickz merged commit fbee9b0 into GitHubSecurityLab:main Jul 27, 2026
13 checks passed
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.

3 participants