Skip to content

Release Apollo Java 2.5.0 #130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nobodyiam merged 1 commit into from
Feb 19, 2026
Merged

Release Apollo Java 2.5.0 #130

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@
</developers>

<properties>
<revision>2.5.0-SNAPSHOT</revision>
<revision>2.5.0</revision>
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ 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.

<java.version>1.8</java.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<spring-boot.version>2.7.18</spring-boot.version>
Expand Down