Release Apollo Java 2.5.0

[nobodyiam]

What's the purpose of this PR

Prepare Apollo Java 2.5.0 release by removing -SNAPSHOT from root revision.

Which issue(s) this PR fixes:

Fixes #N/A (release task)

Brief changelog

• bump version to 2.5.0

Follow this checklist to help us incorporate your contribution quickly and easily:

• Read the Contributing Guide before making this pull request.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit tests to verify the code.
• Run mvn clean test to make sure this pull request doesn't break anything.
• Update the CHANGES log.

Summary by CodeRabbit

• Chores
  • Updated project version to 2.5.0, marking this as a stable release.

[coderabbitai]

📝 Walkthrough

Walkthrough

The Maven project version property is updated from 2.5.0-SNAPSHOT to 2.5.0 in pom.xml, marking the transition from a development snapshot to a release version.

Changes

Cohort / File(s)	Summary
Version Release pom.xml	Updated project revision property from 2.5.0-SNAPSHOT to 2.5.0, designating the release version used by Maven build configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• bump version to 2.3.0 #75: Modifies the same pom.xml revision property to switch from a -SNAPSHOT to a release version
• bump version to 2.4.0 #96: Updates the revision property from -SNAPSHOT to a released version (2.4.0)
• bump version to 2.5.0-SNAPSHOT #99: Related version change where another PR bumps to 2.5.0-SNAPSHOT and this finalizes to 2.5.0

Poem

🐰 From snapshot's haze to release so bright,
The version now shines, polished just right,
No more the dash and the uncertain way,
Two-point-five-zero's here to stay! 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Release Apollo Java 2.5.0' directly and clearly matches the main change: removing -SNAPSHOT from the version property and bumping to 2.5.0 for the release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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 and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.96%. Comparing base (d4b76f8) to head (2dc1875).
⚠️ Report is 21 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #130      +/-   ##
============================================
+ Coverage     68.68%   70.96%   +2.28%     
- Complexity     1503     1632     +129     
============================================
  Files           212      224      +12     
  Lines          6396     6727     +331     
  Branches        647      679      +32     
============================================
+ Hits           4393     4774     +381     
+ Misses         1673     1601      -72     
- Partials        330      352      +22     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@pom.xml`:
- Line 63: CHANGES.md is missing entries for the 2.5.0 release referenced by the
<revision>2.5.0</revision> bump; add one or more Markdown-formatted entries for
this release in CHANGES.md where each entry's link text is the change
description and the link target is the PR URL (not the issue URL), e.g. "[Fix
... detailed summary](https://github.com/.../pull/NNN)"; follow the AGENTS.md
convention and include all PRs/changes that went into 2.5.0, then mark the
"Update CHANGES log" checklist item as done in the contributor checklist.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

CHANGES.md not updated before release.

The contributor checklist explicitly marks "Update CHANGES log" as unchecked. Per project convention, every entry should be a Markdown link whose text is the change description and whose target is the PR URL (not the issue URL), e.g.:

[Fix ... detailed summary](https://github.com/apolloconfig/apollo-java/pull/130)

Please add the 2.5.0 release entries before merging. Based on learnings from AGENTS.md: "Format CHANGES.md entries as Markdown links with link text as change description and link target as PR URL."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@pom.xml` at line 63, CHANGES.md is missing entries for the 2.5.0 release
referenced by the <revision>2.5.0</revision> bump; add one or more
Markdown-formatted entries for this release in CHANGES.md where each entry's
link text is the change description and the link target is the PR URL (not the
issue URL), e.g. "[Fix ... detailed summary](https://github.com/.../pull/NNN)";
follow the AGENTS.md convention and include all PRs/changes that went into
2.5.0, then mark the "Update CHANGES log" checklist item as done in the
contributor checklist.