Skip to content

Conversation

@nickolay168
Copy link
Contributor

@nickolay168 nickolay168 commented Jan 19, 2026

Recently we have started to see the failures of javascript/typescript check of CodeQL: here is one example.

The issue happens because the action github/codeql-action/analyze@v3 does not set the variable to CODEQL_EXTRACTOR_ACTIONS_WIP_DATABASE, which is needed by the new version of CodeQL binary to analyse the GitHub actions. This results in warning and consequent failure to finalize the database: CodeQL detected code written in JavaScript/TypeScript but could not process any of it.

There are two possible soilutions:

  • In the advanced scenario we can set the variable CODEQL_EXTRACTOR_ACTIONS_WIP_DATABASE (this PR).
  • Or we can enable GitHub option in default CodeQL scenario (set through GitHub UI) and disable javascript check as we do not have the java script code in this repository.

I have checked the fix on the forked repository.


This change is Reviewable

@github-actions
Copy link
Contributor

github-actions bot commented Jan 19, 2026

Tip

Preview URL:

@nickolay168 nickolay168 changed the title fix: Setupo custom codeQL with the latest codeql-actions. fix: Setup custom codeQL with the latest codeql-actions. Jan 19, 2026
@github-actions github-actions bot added the bug Bug fix for the user, not a fix to a build script label Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Bug fix for the user, not a fix to a build script

Development

Successfully merging this pull request may close these issues.

1 participant