[tomasz-tylenda-sonarsource]

Problem: java should not match sonar-javascript-plugin

Fix: make plugin-artifacts match exact. plugin-name matching still uses .*

Test: https://github.com/SonarSource/sonar-apex/actions/runs/22671446061 - verfied that plugin-artifacts-sqs: "java,ape.*" updated only java and apex

[hashicorp-vault-sonar-prod]

GHA-200

[nils-werner-sonarsource]

The plugin-artifacts input already exists for listing explicit artifact names. All three reusable workflows (automated-release.yml, cloud-security-automated-release.yml, abd-automated-release.yml) already pass explicit plugin-artifacts, so plugin-name is only used in the sed as a fallback when
plugin-artifacts is empty. Switching to exact matching fixes the bug without any new inputs.

[tomasz-tylenda-sonarsource]

The plugin-artifacts input already exists for listing explicit artifact names. All three reusable workflows (automated-release.yml, cloud-security-automated-release.yml, abd-automated-release.yml) already pass explicit plugin-artifacts, so plugin-name is only used in the sed as a fallback when plugin-artifacts is empty. Switching to exact matching fixes the bug without any new inputs.

Maybe I'm missing something, but based on reading

release-github-actions/update-analyzer/action.yml

Line 76 in b40506f

- name: Update analyzer version in build file

I don't see how using plugin-artifacts-sqs: java would help with not matching javascript. I see that plugin artifacts allows one to specify multiple prefixes, but it does not help with exact matching.

I think I should fix dryRun tickets issue before getting back to this problem, so that I can test things without affecting prod Jira.

[tomasz-tylenda-sonarsource]

The plugin-artifacts input already exists for listing explicit artifact names. All three reusable workflows (automated-release.yml, cloud-security-automated-release.yml, abd-automated-release.yml) already pass explicit plugin-artifacts, so plugin-name is only used in the sed as a fallback when plugin-artifacts is empty. Switching to exact matching fixes the bug without any new inputs.

Maybe I'm missing something, but based on reading

release-github-actions/update-analyzer/action.yml

Line 76 in b40506f

- name: Update analyzer version in build file

I don't see how using plugin-artifacts-sqs: java would help with not matching javascript. I see that plugin artifacts allows one to specify multiple prefixes, but it does not help with exact matching.
I think I should fix dryRun tickets issue before getting back to this problem, so that I can test things without affecting prod Jira.

Ah, now I see how to fix it. Let me update the PR.

[sonarqubecloud]

SonarQube reviewer guide

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tomasz-tylenda-sonarsource]

I update the PR to match plugin artifacts exactly.

[nils-werner-sonarsource]

LGTM!