{{ message }}
Repository navigation
chore(release): prepare Java SDK 0.1.0-rc.1 for Maven Central - #3
Merged
Merged
Conversation
moonyue-w
changed the title
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
1 participant
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.
Prepare the first public Maven Central release candidate as
com.qoder.sdk:qoder-cloud-agents-sdk:0.1.0-rc.1for installation and integration testing before the stable0.1.0release.Align the SDK and example POMs, package and publication checks, namespace gate, README, and maintenance documentation with the selected coordinates. Consolidate the initial changelog under
0.1.0-rc.1. Java packages remain undercom.qoder.cloudagents; the SDK and example implementation is unchanged from main.Validation:
make quality teston JDK 17: repository checks, 545 SDK tests and 62 packaged-consumer tests passed with no failures, errors or skips.Publication remains a separate manual workflow after this PR is merged and main CI succeeds. No Maven Central package or release tag has been created by this PR.