[henrymercer]

The "All-platform bundle" and "CodeQL Bundle All" PR checks are meant to test the all-platform CodeQL bundle. Since #3130, though, prepare-test has returned nightly as the tools URL for nightly-latest regardless of use-all-platform-bundle, so both checks have been testing the platform-specific nightly bundles.

This PR makes prepare-test look up the latest nightly release and return the URL of its all-platform bundle when use-all-platform-bundle is set. It also adds a step to the "All-platform bundle" check that fails unless the bundle contains tools for Linux, macOS and Windows, so that this can't silently regress.

The Ubuntu job of "All-platform bundle" covers everything that "CodeQL Bundle All" tests, so this PR removes "CodeQL Bundle All".

Risk assessment

For internal use only. Please select the risk level of this change:

• Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.

Which use cases does this change impact?

Environments:

• Testing/None - This change does not impact any CodeQL workflows in production.

How did/will you validate this change?

• End-to-end tests - I am depending on PR checks (i.e. tests in pr-checks).

If something goes wrong after this change is released, what are the mitigation and rollback strategies?

• Development/testing only - This change cannot cause any failures in production.

How will you know if something goes wrong after this change is released?

• Other

Are there any special considerations for merging or releasing this change?

• Special considerations - CodeQL Bundle All (ubuntu-26.04, nightly-latest) is a required check, so it needs removing from the required checks with pr-checks/sync-checks.ts before this PR can merge.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Consider adding a changelog entry for this change.
• Confirm the readme and docs have been updated if necessary.

[Copilot]

🟡 Changes recommended

The bundle check uses POSIX dirname on a Windows backslash path, incorrectly checking ./tools and potentially failing Windows PR checks for valid bundles.

1 open issue

• Normalize Windows path separators before resolving the bundle directory · New

What changed in this PR

This PR restores all-platform nightly bundle coverage in the CodeQL Action’s PR checks without changing production behavior.

Changes:

• Resolve an explicit all-platform nightly bundle URL when requested by prepare-test.
• Add a check for Linux, macOS, and Windows tool directories.
• Remove the redundant “CodeQL Bundle All” workflow and its deflake registration.

File	Description
pr-checks/​checks/​all-platform-bundle.yml	Adds validation that the bundle contains tools for all three platforms.
.github/​workflows/​test-codeql-bundle-all.yml	Removes the redundant standalone check.
.github/​workflows/​deflake.yml	Removes the deleted workflow’s retry registration.
.github/​workflows/​__all-platform-bundle.yml	Mirrors the template’s validation step in the generated workflow.
.github/​actions/​prepare-test/​action.yml	Resolves the latest nightly all-platform bundle URL when requested.

_{Review effort: Balanced (auto)}

[ChelbiOracle]

Chelbi Denny

…

On Mon, Nov 9, 2026, 10:58 AM Henry Mercer ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In pr-checks/checks/all-platform-bundle.yml <#4312 (comment)> : > @@ -17,6 +17,18 @@ steps: # Swift is not supported on Ubuntu so we manually exclude it from the list here languages: cpp,csharp,go,java,javascript,python,ruby tools: ${{ steps.prepare-test.outputs.tools-url }} + - name: Check that the bundle contains tools for all platforms + env: + CODEQL_PATH: ${{ steps.init.outputs.codeql-path }} + run: | + # Platform-specific bundles only contain the tools for their own platform. + tools_dir="$(dirname "$CODEQL_PATH")/tools" I think Git Bash's dirname handles this situation, and indeed the Windows job passed. — Reply to this email directly, view it on GitHub <#4312?email_source=notifications&email_token=BUZOJV4LUMRZJFJIU5GDULD5YIATPA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTKOBTGAZDSNZUG42KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussion_r4516099464>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BUZOJV4VHHRBFNOFZQFQ4QD5YIATPAVCNFSNUABFKJSXA33TNF2G64TZHMZDKOJUGQ2TQNZYHNEXG43VMU5TMMRZGEZTGNZQGY2KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BUZOJV4OVWODJEYVQFBENGL5YIATPA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTKOBTGAZDSNZUG42KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/BUZOJV2AL2DCCGF2PUVOHKT5YIATRA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTKOBTGAZDSNZUG42KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>