✔️ Validator: TITLE

• ✔️ All the requisite validations passed for 'or' option
  Input : fix: Setup custom codeQL with the latest codeql-actions.
  Settings : {"or":[{"must_include":{"regex":"^(feat|docs|chore|cleanup|fix|refactor|test|style|perf)(\\([^) ]+\\))?:\\ .+$","message":"Semantic release conventions must be followed."}},{"must_include":{"regex":"^Bump [^ ]* from [^ ]* to [^ ]*$","message":"Dependabot PRs are exempt from semantic release conventions."}}]}

✔️ Validator: COMMIT

• ✔️ Your commit messages met the specified criteria
  Input : fix: Setupo custom codeQL with the latest codeql-actions.
  Settings : {"do":"commit","message":{"regex":"^((feat|docs|chore|cleanup|fix|refactor|test|style|perf)(\\([^) ]+\\))?:\\ .+|Bump [^ ]* from [^ ]* to [^ ]*)","message":"Semantic release conventions must be followed."}}

✔️ Validator: DESCRIPTION

• ✔️ description must exclude '\[ \]'
  Input : 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 

Settings : {"must_exclude":{"regex":"\\\\[ \\\\]","message":"There are incomplete TODO task(s) unchecked."}}