Release Ci pipeline #174
Release Ci pipeline #174
Conversation
Remove manual sbt-release setting
build.sbt
Outdated
| import xerial.sbt.Sonatype.sonatypeCentralHost | ||
| ThisBuild / sonatypeCredentialHost := sonatypeCentralHost |
There was a problem hiding this comment.
@SemyonSinchenko @alfonsorr @MrPowers Either this if we have sonatypeCentral account or
For newer sonatypeAccount
ThisBuild / sonatypeCredentialHost := "s01.oss.sonatype.org"
sonatypeRepository := "https://s01.oss.sonatype.org/service/local"
There was a problem hiding this comment.
If @MrPowers didn't create a new account, you don't need to configure the host with sbt-ci-release because he has an account in the old server and we have to publish there.
There was a problem hiding this comment.
@alfonsorr sure let's me remove this part. I probably going to just keep the generic part and leave the specific setup to whoever have control to these settings
There was a problem hiding this comment.
To me it looks good. Thanks @zeotuan
P.S. Can we have a similar one for tsumugi?
.github/workflows/release.yml
Outdated
| PGP_PASSPHRASE: ${{secrets.PGP_PASSPHRASE}} | ||
| PGP_SECRET: ${{secrets.PGP_SECRET}} | ||
| SONATYPE_PASSWORD: ${{secrets.SONATYPE_PASSWORD}} | ||
| SONATYPE_USERNAME: ${{secrets.SONATYPE_USERNAME}} |
There was a problem hiding this comment.
| PGP_PASSPHRASE: ${{secrets.PGP_PASSPHRASE}} | |
| PGP_SECRET: ${{secrets.PGP_SECRET}} | |
| SONATYPE_PASSWORD: ${{secrets.SONATYPE_PASSWORD}} | |
| SONATYPE_USERNAME: ${{secrets.SONATYPE_USERNAME}} | |
| PGP_PASSPHRASE: ${{secrets.PGP_PASSPHRASE}} | |
| PGP_SECRET: ${{secrets.PGP_LONG_ID}} | |
| SONATYPE_PASSWORD: ${{secrets.MAVEN_PASSWORD}} | |
| SONATYPE_USERNAME: ${{secrets.MAVEN_USERNAME}} |
As @MrPowers provided in Slack
Yeah let's me prepare PR |
|
Lest see if we can release a snapshot version with this pr |
No description provided.