fix: bump package version to 2.2.7 to retry failed Sonatype publish - #88
Open
alexgomezlf wants to merge 1 commit into
Open
fix: bump package version to 2.2.7 to retry failed Sonatype publish#88alexgomezlf wants to merge 1 commit into
alexgomezlf wants to merge 1 commit into
Conversation
The 2.2.6 publish (run 32753248673) failed at the "Publish to Sonatype" step on a retry attempt. Maven Central still only has up to 2.2.4 published, and 2.2.5 never made it either, suggesting the Central Publishing Portal is rejecting re-deployment of a version that already had a failed upload attempt. No functional changes.
Contributor
Contributor
Contributor
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.
The 2.2.6 publish (run 32753248673) failed at the "Publish to Sonatype" step on a retry attempt. Maven Central still only has up to 2.2.4 published, and 2.2.5 never made it either, suggesting the Central Publishing Portal is rejecting re-deployment of a version that already had a failed upload attempt. No functional changes.