chore: configure release-please for example pom.xml - #78
Merged
stenalpjolly merged 1 commit intoSep 9, 2026
Merged
stenalpjolly merged 1 commit into
stenalpjolly merged 1 commit into
Conversation
stenalpjolly
force-pushed
the
stenalpjolly_fix-release-please-example-pom
branch
from
September 9, 2026 10:40
dd75127 to
45544ae
Compare
anubhav756
approved these changes
Sep 9, 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
Configures Release Please to automatically track and synchronize the
mcp-toolbox-sdk-javadependency version inexample/pom.xmlduring release generation by adding it toextra-filesand annotating the dependency with thex-version-updateinline marker.Expectation & Implementation
pom.xmlto the target release version. Becauseexample/pom.xmlwas omitted fromextra-files, its SDK dependency remained pinned to0.3.0-SNAPSHOT. In CI presubmit workflows, step 26 (Build Example with Maven) executescd example && mvn compileimmediately followingmvn install -DskipTests, triggering dependency resolution failures due to missing SNAPSHOT artifacts.<!-- {x-version-update:mcp-toolbox-sdk-java:current} -->to thecom.google.cloud.mcp:mcp-toolbox-sdk-javadependency entry inexample/pom.xml."example/pom.xml"underpackages["."].extra-filesinrelease-please-config.json.example/pom.xmland rewrite the dependency version to match the released package version in lockstep across all release PRs.Test cases
JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64 mvn install -DskipTests -Djacoco.skip=trueto install root SDK artifacts.cd example && JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64 mvn compileand verifiedBUILD SUCCESS.Compile/build,Lint/lint,Google GitHub Admin: Actions Check,cla/google, andconventionalcommits.org.Acceptance criteria
release-please-config.jsonincludes"example/pom.xml"underpackages["."].extra-files.example/pom.xmlcontains the valid<!-- {x-version-update:mcp-toolbox-sdk-java:current} -->marker on themcp-toolbox-sdk-javadependency.Compile/build,Lint/lint, etc.) pass.example/pom.xmlalongside rootpom.xmlduring release PR generation.Breaking changes
None. This is an internal CI and release-tooling configuration update with no changes to the SDK runtime or public API surfaces.