You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Message states v3 will be depreciated December 2026, however this is reported as an error causing workflow fail.
C:\hostedtoolcache\windows\CodeQL\2.23.5\x64\codeql\codeql.exe database finalize --finalize-dataset --threads=2 --ram=6655 D:\a\_temp\codeql_databases\javascript
CodeQL detected code written in C# and GitHub Actions, but not any written in JavaScript/TypeScript. Confirm that there is some source code for JavaScript/TypeScript in the project. For more information, review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build .
Error: Encountered a fatal error while running "C:\hostedtoolcache\windows\CodeQL\2.23.5\x64\codeql\codeql.exe database finalize --finalize-dataset --threads=2 --ram=6655 D:\a\_temp\codeql_databases\javascript". Exit code was 32 and last log line was: CodeQL detected code written in C# and GitHub Actions, but not any written in JavaScript/TypeScript. Confirm that there is some source code for JavaScript/TypeScript in the project. For more information, review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build . See the logs for more details.
Do you have more information to share? E.g. is this with a .NET 10 project? Ideally, if this is a public repo, a link to the repo / workflow would be great to help us troubleshoot your problem.
Activity
mbg commentedon Nov 14, 2025
Hi @brian-welsh 👋
The error you posted doesn't isn't related to the forthcoming v3 depreciation.
It looks like it could be related to #3207.Do you have more information to share? E.g. is this with a .NET 10 project? Ideally, if this is a public repo, a link to the repo / workflow would be great to help us troubleshoot your problem.
brian-welsh commentedon Nov 14, 2025
correct. sorry about that, there are 2 issues. the the error quoted is one, that appears whether v3 or v4 is used.
v3 produced the errors shown in screen grab.
I'll separate these out into separate issues.
brian-welsh commentedon Nov 14, 2025
I'm going to close this down to dive down the rabbit hole to gather more detailed info.