[hashicorp-vault-sonar-prod]

The latest CI run on master is red: QA - Plugin [Linux] - SQ: DEV (run 103833096253).

This PR was opened with an empty commit to reserve a place for the CI fix.

[hashicorp-vault-sonar-prod]

gitar auto-apply:on

[hashicorp-vault-sonar-prod]

gitar master CI is failing: https://github.com/SonarSource/sonar-xml/actions/runs/34551835240/job/103290947497

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. If you can't fix it, leave a comment explaining your investigation.
5. If there's nothing to fix, reply with "This PR can be closed now" and your investigation notes.

[hashicorp-vault-sonar-prod]

SONARXML-453

[sonarqube-next]

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-bot]

Investigated the failure. This is not a real code issue in this repo — it's a flaky/environmental failure tied to the SQ: DEV SonarQube build target.

Findings:

• The failing test is ProfileRegistrarTest.testPluginRegistersRuleInDefaultXmlProfile, which asserts that a built-in "Sonar way" profile exists for the xml language via the WS API.
• Master (7ff7ca0) has been unchanged since Sep 9. That exact commit passed on QA - Plugin [Linux] - SQ: LATEST on the initial push run, and SQ: DEV itself passed on this same commit on Sep 7–9 scheduled runs.
• Starting Sep 10, only the SQ: DEV variant of this job began failing on the same commit, while SQ: LATEST continues to pass consistently. Since SQ: DEV tracks a moving/nightly SonarQube build (not pinned to this repo's code), and no relevant source changed between the passing and failing runs, the regression originates upstream in the SonarQube DEV build/environment, not in sonar-xml.
• I triggered a rerun of the failed job (gh run rerun -j 103290947497) to confirm — it's still in progress at the time of this comment.

This PR can be closed now. No code change is needed in sonar-xml; this looks like a transient/upstream SQ: DEV issue. If it keeps failing on subsequent scheduled runs, it would be worth flagging to the SonarQube DEV build owners rather than fixing here.

[hashicorp-vault-sonar-prod]

gitar auto-apply:on

gitar master is still at 7ff7ca01dc30, but the failed run changed from 103290947497 to 103294990696, and its latest CI is still failing: https://github.com/SonarSource/sonar-xml/actions/runs/34551835240/job/103294990696

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. If you can't fix it, leave a comment explaining your investigation.
5. If there's nothing to fix, reply with "This PR can be closed now" and your investigation notes.

[hashicorp-vault-sonar-prod]

gitar auto-apply:on

gitar master has advanced from 7ff7ca01dc30 to b16b319651cb, and its latest CI is still failing: https://github.com/SonarSource/sonar-xml/actions/runs/34797256861/job/103833096253

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. If you can't fix it, leave a comment explaining your investigation.
5. If there's nothing to fix, reply with "This PR can be closed now" and your investigation notes.