gitar auto-apply:on

gitar master CI is failing: https://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.javascript%3Ajavascript&branch=dogfood-on-peach

1. Investigate the failure.
2. If it looks transient or flaky, retry it.
3. If it's a real issue, fix it in this PR.
4. After pushing a fix, recheck the PR's CI status, and keep pushing commits until it passes.
5. If you can't fix it, leave a comment explaining your investigation.
6. If there's nothing to fix, reply with "This PR can be closed now" and your investigation notes.

JS-2470

This PR can be closed now.

Investigation notes:

• The referenced run corresponds to the Build workflow on master for commit 79fe811 (PR Update SonarSource/parent-oss monorepo to v11.10.0.86299 #7953), run 34840515151.
• That run completed with an overall success status. All required jobs passed, including Analyze in SonarQube NEXT and the full QA/Ruling matrix.
• The only annotation on the run is Releasability checks of 14.0.0.45932 failed, coming from the Releasability status job. That job itself completed successfully (green) — it's reporting the release-readiness status (e.g. pending dogfood/quality-gate confirmation), not a build or test failure in this repository.
• The linked SonarQube dashboard (dogfood-on-peach branch) is the routine dogfood analysis target for this build, not a red/failing check.

No code or CI configuration issue was found to fix in this PR.

Ruling Report

No changes to ruling expected issues in this PR

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

gitar auto-apply:on

gitar master has advanced from 79fe811cad67 to 6b11c6ee96a4, and its latest CI is still failing: https://github.com/SonarSource/SonarJS/actions/runs/34951830854/job/104326385425

1. Investigate the failure.
2. If it looks transient or flaky, retry it.
3. If it's a real issue, fix it in this PR, replacing any obsolete fix if the failure has changed.
4. After pushing a fix, recheck the PR's CI status, and keep pushing commits until it passes.
5. If you can't fix it, leave a comment explaining your investigation.
6. If there's nothing to fix, leave a comment with your investigation notes, ending it with exactly "let's close this PR".

gitar auto-apply:on

gitar master is still at 6b11c6ee96a4, but the failed run changed from 104326385425 to 104382878178, and its latest CI is still failing: https://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.javascript%3Ajavascript&branch=dogfood-on-peach

1. Investigate the failure.
2. If it looks transient or flaky, retry it.
3. If it's a real issue, fix it in this PR, replacing any obsolete fix if the failure has changed.
4. After pushing a fix, recheck the PR's CI status, and keep pushing commits until it passes.
5. If you can't fix it, leave a comment explaining your investigation.
6. If there's nothing to fix, leave a comment with your investigation notes, ending it with exactly "let's close this PR".

gitar auto-apply:on

gitar master has advanced from 6b11c6ee96a4 to 10fe3957b5e1, and its latest CI is still failing: https://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.javascript%3Ajavascript&branch=dogfood-on-peach

1. Investigate the failure.
2. If it looks transient or flaky, retry it.
3. If it's a real issue, fix it in this PR, replacing any obsolete fix if the failure has changed.
4. After pushing a fix, recheck the PR's CI status, and keep pushing commits until it passes.
5. If you can't fix it, leave a comment explaining your investigation.
6. If there's nothing to fix, leave a comment with your investigation notes, ending it with exactly "let's close this PR".