Skip to content
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

Support for Sonatype Central #294

Closed
KacperFKorban opened this issue Mar 18, 2024 · 8 comments · Fixed by #304
Closed

Support for Sonatype Central #294

KacperFKorban opened this issue Mar 18, 2024 · 8 comments · Fixed by #304

Comments

@KacperFKorban
Copy link
Contributor

It seems that Sonatype's Jira is being deprecated in favour of Sonatype Central. (docs) The intention is to make Sonatype Central the main/only way to publish artifacts. It would be great to be able to publish to Sonatype Central using sbt-ci-release

There already exists a PR with the support for Sonatype Central API in sbt-sonatype: xerial/sbt-sonatype#474

@Andrapyre
Copy link
Contributor

Refactoring here should be very minimal, once sbt-sonatype has a new release, as the current implementation in this PR supports running sonatypeBundleRelease to deploy artifacts to Sonatype Central.

Sonatype Central does not support publishing snapshots however, so any logic around snapshot publication will need to be refactored, but that, again, looks very minimal.

@KacperFKorban
Copy link
Contributor Author

KacperFKorban commented Mar 23, 2024

Refactoring here should be very minimal, once sbt-sonatype has a new release, as the current implementation in xerial/sbt-sonatype#474 supports running sonatypeBundleRelease to deploy artifacts to Sonatype Central.

@Andrapyre I thought as much. I think that the sbt-ci-release documentation might require the most changes. It is linked in many other repositories and is considered a "Scala Sonatype publishing source of truth".

BTW, thanks for implementing xerial/sbt-sonatype#474 ❤️

@Andrapyre
Copy link
Contributor

Good point about reproducing sonatype docs here, though I also don't see that requiring much investment, as the current implementation just requires users to change the sonatype host in order for everything to work out of the box.

datYori added a commit to raw-labs/snapi that referenced this issue Jun 17, 2024
Since latest Sonatype infra migration, the current usage of
`sbt-ci-release` plugin is not working anymore
We might still face this issue until
sbt/sbt-ci-release#294 is solved,
To cope with this we publish packages to Github Apache Maven
@xuwei-k
Copy link
Member

xuwei-k commented Jun 29, 2024

@eed3si9n
Copy link
Member

#303 landed, but given xerial/sbt-sonatype#507 we might need to update.

@mbaechler
Copy link

Good point about reproducing sonatype docs here, though I also don't see that requiring much investment, as the current implementation just requires users to change the sonatype host in order for everything to work out of the box.

Hi @Andrapyre, I'm trying to make use of sbt-ci-release to publish my lib and I may not understand what you mean by

requires users to change the sonatype host in order for everything to work out of the box

Are you referring to something like

ThisBuild / sonatypeCredentialHost := sonatypeCentralHost

Maybe I did a stupid mistake but I can't make it work, I always get "Repository for publishing is not specified."

For reference, the project is here https://github.com/PerformanceIMMO/pg-event-store and the failing publish logs are here https://github.com/PerformanceIMMO/pg-event-store/actions/runs/10847421290/job/30102632825

Thanks for your help.

@Andrapyre
Copy link
Contributor

@mbaechler , the link is coming up as not found for some reason. Is this a private repo?

@mbaechler
Copy link

mbaechler commented Sep 13, 2024

@Andrapyre yes, sorry, it was private by mistake.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants