build: downgrade maven-release-plugin to 2.5.3

[nikagra]

Summary

• Reverts maven-release-plugin from 3.3.1 → 2.5.3 as a short-term workaround to restore the broken release flow on Maven 3.9.16.
• Tracks: build: upgrade maven-release-plugin from 2.5.3 to a compatible 3.x version #935

Problem

After bumping to 3.3.1 (released end of May 2026), release:perform fails with:

Cannot perform release - the preparation step was stopped mid-way.
Please re-run release:prepare to continue, or perform the release from an SCM tag.

Root Cause

pom.xml pins maven-scm-provider-gitexe:1.9.5, which implements the SCM 1.x API. maven-release-plugin 3.x requires the SCM 2.x API internally. The mismatch causes release:prepare to abort mid-lifecycle, leaving the build in a state that blocks release:perform.

Workaround

Revert to 2.5.3, which is compatible with maven-scm-provider-gitexe:1.9.5 (SCM 1.x). This is a temporary measure — see #935 for the proper 3.x upgrade path (requires upgrading both the plugin and maven-scm-provider-gitexe to 2.x together).

Test plan

• Trigger a release build on the CI runner (Maven 3.9.16) to confirm release:prepare → release:perform completes without error.

[coderabbitai]

Warning

Review limit reached

@nikagra, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 54 minutes and 3 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 196a66e5-fa51-4302-a993-1fb5b0eef063

📥 Commits

Reviewing files that changed from the base of the PR and between 46b7f7d and 8cc74a7.

📒 Files selected for processing (1)

• pom.xml

📝 Walkthrough

Walkthrough

The maven-release-plugin version in pom.xml is downgraded from 3.3.1 to 2.5.3. This reverts a prior upgrade that broke the release flow because maven-release-plugin 3.x requires the SCM 2.x API, which is incompatible with the pinned maven-scm-provider-gitexe:1.9.5 dependency that implements SCM 1.x. The revert restores the last known-working version until a coordinated upgrade of both artifacts can be performed.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely states the main change: downgrading the maven-release-plugin to 2.5.3.
Linked Issues check	✅ Passed	The PR matches #935's short-term fix by reverting maven-release-plugin to 2.5.3 to restore release flow.
Out of Scope Changes check	✅ Passed	The changes are limited to the requested plugin version revert and contain no unrelated modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The description matches the change by explaining the downgrade of maven-release-plugin from 3.3.1 to 2.5.3.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}