Skip to content

Prepare publishing through the new Maven Central Portal. #5214

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

Merged
merged 3 commits into from
Jul 24, 2025

Conversation

sjrd
Copy link
Member

@sjrd sjrd commented Jul 24, 2025

I could successfully publish a 1.20.0-SNAPSHOT with those changes. It remains to be seen whether publishing a real version will work, but that's hard to test before we actually get to the real version.

@sjrd sjrd requested a review from gzm0 July 24, 2025 10:52
@sjrd sjrd force-pushed the prepare-for-maven-central-portal branch from 1aeb1c6 to d420c35 Compare July 24, 2025 12:17
echo "If you're publishing a non-snapshot release, now you need to execute:"
echo " sbt sonaUpload"
echo "then go to https://central.sonatype.com/publishing,"
echo "double-check the contents, and click 'Publish'."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😱 that looks annoying :-/

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not very different from before. There's only the sonaUpload step to do in addition, but that should be faster than what we had before.

We can also do sonaRelease and then everything else is automated. But given the complexity of the artifact setup in this repo, I have always preferred double-checking.

sjrd added 3 commits July 24, 2025 18:40
The new Maven Central Portal does not allow publishing artifacts under
the legacy sbt plugin path pattern. sbt < 1.9.0 will not be able to
resolve the new path patterns, so support for it is broken anyway.

We explicitly drop support for it internally, instead of pretending
that it will still work.
This is necessary to publish through the new Maven Central Portal.
@sjrd sjrd force-pushed the prepare-for-maven-central-portal branch from d420c35 to 67ecb76 Compare July 24, 2025 16:40
@sjrd sjrd enabled auto-merge July 24, 2025 16:41
@sjrd sjrd merged commit 63e75bf into scala-js:main Jul 24, 2025
3 checks passed
@sjrd sjrd deleted the prepare-for-maven-central-portal branch July 25, 2025 10:21
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 this pull request may close these issues.

2 participants