Only publish toolkit to Maven Central, add unified release script#805
Merged
Only publish toolkit to Maven Central, add unified release script#805
Conversation
- Set maven.deploy.skip=true by default, override to false only in apm-application-toolkit. Agent and plugins are distributed via download package and Docker images, not Maven Central. - Add tools/releasing/release.sh with two-step release flow: prepare-vote (preflight + prepare + stage + upload + vote email) and vote-passed (promote + docker + announce email + cleanup). - Remove create_release.sh (logic merged into release.sh stage). - Update release-java-agent.md documentation.
kezhenxu94
approved these changes
Apr 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
apm-application-toolkitmodules to Maven Central. Agent, plugins, and core modules are distributed via download package and Docker images — no need to publish them to Maven.tools/releasing/release.shwith two-step flow matching the ASF vote process:prepare-vote <version> [next_version]— preflight checks, branch, maven release:prepare, build tars, upload to SVN, generate vote emailvote-passed [old_version]— promote SVN, push Docker images, generate announce email, cleanup old releasecreate_release.sh(logic merged intorelease.sh stage)release-java-agent.mddocumentationTest plan
release.sh preflightruns successfullyrelease.shhelp output shows all commandsmaven.deploy.skipworks correctly during next release🤖 Generated with Claude Code