Migrate to publishing via new Sonatype Central publishing portal #294
Conversation
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
chadlwilson
force-pushed
the
migrate-to-sonatype-central-publishing
branch
from
ba96e58 to
75a1aec
Compare
chadlwilson
force-pushed
the
migrate-to-sonatype-central-publishing
branch
from
75a1aec to
1ab3718
Compare
Member
|
will need to delegate this one, last release I did the existing sonatype setup worked just fine... 🤷 |
Contributor
Author
|
OSSRH was supposed to be EOL June 30. Moreso, if jruby-rack shares a namespace with JRuby core, and core is already using the new Portal than jruby-rack will need to also, since even if the deadline has been extended, each namespace was migrated to the new portal as a whole. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I believe jruby-rack and jruby share a namespace, and jruby was migrated in jruby/jruby@bea5408 so presume this needs to be done here too.
Have assumed the same
centralID for creds as JRuby Core is using, in contrast with the earlierossrhcredential identifier.