Repository navigation
feat: add actions-custom-queries@1.1.2 to central config - #19
Merged
Merged
Conversation
zhongliang02
approved these changes
Sep 16, 2026
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
Adds the GitHub Actions custom-queries pack to the central config:
packs: javascript: - opengovsg/nextjs-custom-queries@1.0.1 - opengovsg/react-custom-queries@1.0.1 - opengovsg/javascript-custom-queries@1.0.3 - opengovsg/nestjs-custom-queries@1.0.0 + actions: + - opengovsg/actions-custom-queries@1.1.2This is the deployment half of the
actions-custom-queries@1.1.2release (codeql-pack PR #42). The pack was broken org-wide at1.1.1(stalecodeql/actions-all@0.4.33lock pin → "database is not compatible with a QL library" → total actions-scan blackout);1.1.2fixes it and is now published on GHCR. The pack was pinned nowhere until this PR, so this is a brand-new pin (out of scope for the pack pipeline's auto-reconciler, which only bumps existing pins) — hence a manual add.E2E evidence (real scan on
security-codeql-test-actions, CodeQL CLI 2.27.0)Run: https://github.com/opengovsg/security-codeql-test-actions/actions/runs/34494667174 — success. (Validated via a throwaway PR that re-pointed that repo's
config-fileat this branch's commit; PR closed, branch deleted — no lasting change to the test repo.)Pack resolved from GHCR + loaded + executed (run log):
Installed fresh opengovsg/actions-custom-queries@1.1.2— downloaded from GHCR on a clean runner.[1/20] Loaded … unpinned-global-install.qlx,[2/20] … unfrozen-package-install.qlx,[3/20] … unvetted-package-exec.qlx— 20 queries loaded = 17 built-in + 3 custom.Starting evaluation of …/{unfrozen,unpinned,unvetted}.ql→Evaluation done→Interpreted problem query …— all 3 executed (not installed-and-skipped).Findings (code-scanning alert set == local re-analysis with identical 1.1.2 source):
actions/unfrozen-package-installbad-npm-install.yml:8,bad-yarn-install.yml:8(known-bad)actions/unvetted-package-execbad-npx-exec.yml:8–14(known-bad)actions/unpinned-global-installactivesg-nightly/previewworkflowsgood-npm-ci/good-npx-exec/good-pnpm-frozenDeployment note
prodis the org-wide deploy — every repo referencingconfig-file: …@prodpicks up the actions pack on its next scan. Branch cut fromprod; the diff is exactly the added pin.