SC-51500 Skip Maven version update when pom.xml is absent

[hedinasr]

Summary

• Add a Check for pom.xml step to config-maven before the version update step
• Only invoke set_maven_project_version.sh when pom.xml exists (or when the action is re-entered with skip=true)
• Aligns behavior with the existing config-npm guard for package.json

Test plan

• Run config-maven in a repo with a root pom.xml — version update should still run
• Run config-maven in a repo without a root pom.xml — should log skip message and not fail

[hashicorp-vault-sonar-prod]

SC-51500

[Copilot]

Pull request overview

Updates the config-maven composite action to avoid failing (or doing unnecessary work) in repositories that don’t have a pom.xml in the configured working directory, matching the existing config-npm “check manifest before version bump” behavior.

Changes:

• Add a Check for pom.xml step that records whether pom.xml exists in inputs.working-directory.
• Gate the Maven version update step so it only runs when pom.xml is present (or when the action is re-entered with skip=true).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

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

See analysis details on SonarQube Cloud

[gitar-bot]

Code Review ✅ Approved

Prevents Maven version updates in repositories lacking a pom.xml by adding an existence check before execution. No issues found.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}