-
Notifications
You must be signed in to change notification settings - Fork 21
Publish to Sonatype #26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Also change organization name to `com.github.sbt`
Anyone with write access to the repository can cut a release.
|
Related PR for Scala Steward migration: scala-steward-org/scala-steward#3067 |
pvlugter
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks!
|
Thank you for the review! Before you merge, you will have to set the secrets PGP_PASSPHRASE and PGP_SECRET as explained here: https://github.com/sbt/sbt-ci-release#secrets |
|
Hey, would you have some time available soon to set the secrets and try publishing a milestone release? |
I do not have access to |
|
I think I've set up the Sonatype creds a while back, but it's missing GPG signing key. Let me create that too. |
|
Added a GPG signing key. |
Co-authored-by: Enno Runne <458526+ennru@users.noreply.github.com>
|
Thank you Enno and Eugene for your help! |
|
I am going ahead, merging and trying to release an M1 version to see if the workflow works. |
|
After a couple of trial and errors, version 0.1.7 is on its way to Maven Central. |
|
@julienrf great, thanks! |
Also change organization name to
com.github.sbtRelates to #23, fixes #24