add publish workflow - #50
Open
chrjohn wants to merge 4 commits into
Open
Conversation
Co-authored-by: chrjohn <6644028+chrjohn@users.noreply.github.com>
Co-authored-by: chrjohn <6644028+chrjohn@users.noreply.github.com>
…t-publishing Fix fix-standard artifact publishing by migrating from OSSRH to Central Publishing Portal
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.
Sonatype permanently retired the legacy OSSRH service (
oss.sonatype.org), which the parentpom.xmlrelied on vianexus-staging-maven-pluginto publish thefix-standardartifact. Deploys against that plugin now fail since the target service no longer exists.Publishing plugin
org.sonatype.plugins:nexus-staging-maven-pluginwithorg.sonatype.central:central-publishing-maven-plugin(0.11.0)Distribution management
distributionManagementsnapshot repository to point athttps://central.sonatype.com/repository/maven-snapshots/(idcentral)repository(release) entry, since release publishing is now handled by the publishing plugin itselfSigning
maven-gpg-pluginsigning in thereleaseprofile untouched — Central Publishing still requires signed artifactsNote: publishing will also require the maintainer to add
centralserver credentials (Central Portal token) to their Mavensettings.xml/CI secrets, replacing the oldossrhcredentials — outside the scope of this repo change.