This started happening this week, it used to work well before this week (September 22, 2025) ALM used is GitHub Languages of the repositories is TypeScript This is happening in all repos we have associated to projects Error observed: When PRs are created, SonarQube’s quality gate is not passin…

Hey @cvarela-usesi Thanks for the report. By any chance do you use GitHub Actions and also upgarde to sonarqube-scan-action@v6 this week? If not, what CI are you using? And what is the warning here? [image] Thanks! :smiley:

I came here to report this same issue. We’ve recently noticed that every repo is flagging issues that already existed and were flagged 1-2 years ago. When looking into this, we can see that lots of TypeScript rules have been updated as of 22nd September 2025, but also that the “Available since” dat…

Hey there. Alright. After doing some digging, I expect that this is a combination of two things: The Javascript/Typescript analyzer recently added a lot of new rules (and even when there are new rules, backdating kicks in, explaining why you see dates of “1 year ago”) I would guess that you haven…

Hey Colin, this is the message in the Warning: Last analysis has warnings At least one referenced/extended tsconfig.json was not found in the project. Please run ‘npm install’ for a more complete analysis. Check analysis logs for more details. Regarding CI, no, I don’t integrate SonarQube with G…

We seem to be hitting a possibly related issue with typescript projects. We run the same scan on pull requests and when it is merged to main branch. On both it is saying 0% coverage on code, despite us uploading an lcov report with coverage Other teams with non typescript code are still showing co…

@anthony-nhs I don’t see a super clear connection to this thread. It would probably make sense for you to open a new one – and make sure you check the logs as in this guide! [image] How to find logs about importing code coverage Guides When coverage data isn’t…

The connection was it started happening on 22 September when nothing changed on our side

A scan at Mon, 22 Sep 2025 10:06:38 GMT worked showed correct coverage, but our next one at Mon, 22 Sep 2025 10:40:59 GMT showed 0% coverage

This is what I did and worked for me: I removed the review for the PR I was having issues with from my SonarQube portal I committed a non functional commit in my main branch (just a change in the .gitignore file) That triggered a new analysis in my main branch (and passed the quality gate) I went …

Hey @anthony-nhs I wonder if it’s related to this. [image] Error when starting Sonar analysis sonarqube-cloudSonarQube Cloud Hey there. Hello, From your logs, I see sonar.scanner.skipNodeProvisioning is set to true, which makes the scanner use your system’…

Sudden change in quality gate for PRs, "New code" filter is not working

SonarQube Cloud

anthony-nhs (Anthony Nhs) September 25, 2025, 12:20pm 12

fair comment about a new thread - have created Code coverage stopped working for typescript projects

Topic		Replies	Views
Quality gates only for code in changed in Pull Request SonarQube Cloud	17	3682	February 28, 2024
PR analysis fails for existing issues unrelated to current PR SonarQube Cloud coverage	3	68	February 3, 2026
On a PR quality gate, seeing "new code" that is not in the Pull Request SonarQube Cloud sonarqube-cloud	4	1064	July 16, 2021
Pull-Request "new issues" are not a delta of new code SonarQube Cloud pull-request , quality-gate , sonarqube-cloud	3	248	June 19, 2024
Block Pull request based on Quality gate code coverage on new code SonarQube Server / Community Build coverage , quality-gate , new-code	17	2746	September 6, 2022

Sudden change in quality gate for PRs, "New code" filter is not working

Related topics