Repository navigation
ci: update the central-publishing plugin past a response it cannot read - #3
Merged
Merged
Conversation
0.1.0 is on Maven Central, and the build that put it there reports failure. The deployment succeeded, the portal published it, and the plugin then choked reading the status response: UnrecognizedPropertyException: Unrecognized field "warnings" (class DeploymentApiResponse), not marked as ignorable The portal's API grew a field that the client from 0.6.0 does not know and does not ignore. 0.11.0 knows it. Left alone, every future release would publish correctly and then fail its own build, which is the worst shape a release job can have: nobody would trust the red, and eventually nobody would read it.
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.
com.camelmailer:camelmailer-java:0.1.0is on Maven Central (jar, sources, javadoc and both signatures all resolve, and a throwaway project compiles against it). The build that published it nevertheless reports failure.The deployment succeeded and the portal published it; the plugin then choked reading the status response:
The portal's API grew a field the client shipped in 0.6.0 does not know and does not ignore. 0.11.0 is the current release and knows it.
Left alone, every future release would publish correctly and then fail its own build. That is the worst shape a release job can have: nobody trusts the red, and eventually nobody reads it.
Same class of problem as the clippy and ruff breakages earlier today: a tool aged relative to the service it talks to, with no code change on our side.