Repository navigation
ci(codeql): scan without npm install; codeql-action v2 -> v4 - #1490
Merged
Jayanth Reddy Bujula (jbujula) merged 2 commits intoOct 6, 2026
Merged
Conversation
The CodeQL workflow has failed on every run since 2026-09-15 at `npm install` (E401 fetching @microsoft/powerplatform-cli-wrapper from GitHub Packages) because GPR_ACCESS_TOKEN expired, so main has had no CodeQL analysis since 2026-09-12. JavaScript/TypeScript is extracted directly from source (build-mode: none) and codeql-config.yml already limits analysis to src/, so the install and build steps contributed nothing to the scan. Drop them and the os matrix entry that only selected the npm version, and move to codeql-action v4 since v2 is deprecated. Bump checkout to v4 to match the other workflows. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
heiwang
approved these changes
Oct 6, 2026
Brad Flood (brflood)
approved these changes
Oct 6, 2026
Jayanth Reddy Bujula (jbujula)
deleted the
users/jbujula/codeql-build-mode-none
branch
October 6, 2026 21:37
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
3 participants
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.
Why
CodeQL on
mainhas not completed since 2026-09-12. Every run since 2026-09-15 (scheduled, push and PR) fails atnpm install, before the analysis step:GPR_ACCESS_TOKENhas expired, so the repo currently has no fresh CodeQL results, which is now raised as a Continuous SDL (S360) compliance item.Change
npm installandnpm run buildfromcodeql.yml. CodeQL extracts JavaScript/TypeScript straight from source (build-mode: none), and.github/codeql/codeql-config.ymlalready limits analysis tosrc/and ignoresout/dist/build/node_modules, so the install/build output was never part of the scan.github/codeql-action/init+analyze: v2 -> v4. v1/v2 are deprecated and already emit an error annotation on every run.actions/checkout: v3 -> v4, matching the repo's other workflows.osmatrix entry; it only chose between npm@8 and npm@9. The check is now namedAnalyze (javascript)(not a required check).With no secret involved, the scan also works on Dependabot and fork PRs.
Validation
CodeQLrun exercises the new workflow (pull_requesttrigger).mainproduces a fresh analysis.Notes
build (ubuntu-latest)/build (windows-latest)checks will still fail with the same E401:PullRequest.ymlalso usesGPR_ACCESS_TOKEN. That is handled separately by ci: replace expiring GPR_ACCESS_TOKEN PAT with GITHUB_TOKEN #1449 (switch toGITHUB_TOKEN, which needs the package's Manage Actions access grant) or by rotating the secret. It is independent of this change.codeql.ymlpart of ci: replace expiring GPR_ACCESS_TOKEN PAT with GITHUB_TOKEN #1449.