0.12.12

Author: lihaoyi

changelog.adoc

@@ -13,6 +13,65 @@ _The changelog below is for tagged, stable releases. For unstable releases,
 see the list at https://repo1.maven.org/maven2/com/lihaoyi/mill-dist_
 
 
+[#0-12-12]
+=== 0.12.12 - 2025-05-18
+:version: 0.12.12
+:milestone-name: 0.12.12
+:milestone: 115
+:prev-version: 0.12.11
+
+* Backport `mill.scalalib.SonatypeCentralPublishModule/` from `main` ({link-pr}/5107[#5107]). With
+  the https://central.sonatype.org/news/20250326_ossrh_sunset/[Sunset of `oss.sonatype.org`],
+  all Mill projects still on `oss.sonatype.org` will need to migrate their sonatype namespaces
+  (e.g. `com.lihaoyi`) to `central.sonatype.org` to continue publishing. Instructions for this migration
+  are shown below:
+
+** *WARNING: this migration is one-way and cannot be paused or rolled back. If you begin these
+   steps, you must complete them, otherwise your project will be in an un-publishable state.
+   Please read through all steps and ensure you have time to complete them all before you begin*
+
+** (Optional) Upgrade to Mill `0.12.12`, which contains the latest `mill.scalalib.SonatypePublishModule/`
+   command. This is optional because you can use it in earlier versions of Mill (>=0.12.6) as
+   a `mill.contrib` moule, but upgrading is better as it ensures the command you use will be
+   forwards compatible to future versions of Mill.
+
+** Log into the new `central.sonatype.org` web UI (it uses your existing `oss.sonatype.org` username and password)
+   and migrate your namespace from `oss.sonatype.org` via
+   the instructions here https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/.
+   You will then no longer see your namespace on the `oss.sonatype.org` website and it will now be visible
+   in the `central.sonatype.org` website
+
+** Generate a new user token from the `central.sonatype.org` web UI, and replace the
+   old `oss.sonatype.org` tokens everywhere in your publishing infrastructure (e.g. local
+   scripts, Github Actions secrets, etc.)
+
+** Replace all usage of `./mill mill.scalalib.PublishModule/` with `./mill mill.scalalib.SonatypeCentralPublishModule/`
+   everywhere it is use (local scripts, Github Actions config, etc.). You should now be able to
+   publish to `central.sonatype.org`, see in-progress and completed published artifacts in the
+   `central.sonatype.org` website.
+
+*** If you chose not to upgrade Mill to `0.12.12`, instead of `./mill mill.scalalib.SonatypeCentralPublishModule/`
+    you will need to use `./mill --import "ivy:com.lihaoyi::mill-contrib-sonatypecentral:" mill.contrib.sonatypecentral.SonatypeCentralPublishModule/publishAll --publishArtifacts __.publishArtifacts`,
+    and will need to switch to `./mill mill.scalalib.SonatypeCentralPublishModule/` anyway when later
+    upgrading to Mill 1.0.0 and above.
+
+** Note that `central.sonatype.org` is significantly stricter than `oss.sonatype.org` in validating
+   published artifacts (details below). This should not affect 99% of projects out there which uses
+   the default configuration, but may affect you if you use Maven Central to publish other non-jar
+   artifacts (executables, zip files, etc), and cause confusing errors visible in the
+   `central.sonatype.org` web portal. Below is a list of the incompatibilities that I am aware of.
+
+*** `central.sonatype.org` now requires a `pom.xml` to be present with every artifact
+
+*** `central.sonatype.org` now requires all files associated with an artifact to follow the
+    `<artifact-name>-<artifact-version>` name prefix convention, whereas previously any name
+    was accepted
+
+*** `central.sonatype.org` does not allow non-standard `jar` files (e.g. graal native binaries,
+    prepended assembly jars to be published with the `.jar` suffix, and they must instead be
+    published with some other suffix via `def extraPublish`
+
+
 [#0-12-11]
 === 0.12.11 - 2025-05-10
 :version: 0.12.11