build: align release plugins with the other Java repos - #3
Merged
Merged
Conversation
central-publishing-maven-plugin 0.7.0 fails to parse the Central API's new 'warnings' response field (the 1.0.1 deploy succeeded but the job went red). Bump it to 0.11.0 and maven-source-plugin to 3.4.0, matching java-sqs.
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.
central-publishing-maven-plugin0.7.0 cannot parse the newwarningsfield in the Central API response, so the v1.0.1 release job went red after a successful upload (UnrecognizedPropertyException).central-publishing-maven-plugin0.7.0 → 0.11.0maven-source-plugin3.3.1 → 3.4.0The
releaseprofile is now identical tobabelqueue-java-sqs.