Repository navigation
release: publish Maven plugin v0.1.1 - #5
Merged
Merged
Conversation
xiaoyumuxi
marked this pull request as ready for review
October 20, 2026 17:10
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
Publish Maven plugin v0.1.1 after the Java SDK 0.1.0 lock was merged in PR #4.
This release keeps the plugin API and Maven provider behavior unchanged. It only aligns the plugin manifest and both Maven module versions for a new release tag; the packaged backend continues to use the officially released Java SDK 0.1.0 with its pinned URL and SHA-256.
Validation
node scripts/test-process.mjsnode scripts/package.mjsnode scripts/test-backend.mjsnode scripts/test.mjsnode scripts/package.mjs --expect-tag v0.1.1All checks passed locally on Java 17. The release workflow will additionally cover Java 8 and Java 17.