Hi there. I have been publishing to OSSRH until March. Apparently, the old system is no longer functional. I tried to apply the new settings according to sbt Reference Manual — Using Sonatype . But I’m stuck somewhere:
$ sbt sonaUpload
[info] welcome to sbt 1.11.7 (Debian Java 11.0.18)
[info] loading settings for project global-plugins from build.sbt...
[info] loading global plugins from /home/hhrutz/.sbt/1.0/plugins
[info] loading settings for project fscape-next-build from plugins.sbt...
[info] loading project definition from /home/hhrutz/Documents/devel/FScape-next/project
[info] loading settings for project fscape from build.sbt...
[info] resolving key references (10519 settings) ...
[info] set current project to FScape (in build file:/home/hhrutz/Documents/devel/FScape-next/)
[info] uploading bundle to the Central Portal (attempt: 1)
[info] uploading bundle to the Central Portal (attempt: 2)
[info] uploading bundle to the Central Portal (attempt: 3)
gigahorse.StatusError: Unexpected status: 401
```
I tried to create the credentials file and use it like credentials += Credentials(Path.userHome / “.sbt” / “sonatype_central_credentials”) with
host=central.sonatype.com
user=sciss
password=XXX
I have the feeling I need to change this somehow to use some token? Do I need to create new tokens? The new dashboard in https://central.sonatype.com/usertoken is empty.
Appreciate your fingertree library work - used that in a couple of my own projects. Nice work.
I was going to suggest gha-scala-library-release-workflow but I think you’re using Codeberg these days, so…
Just checking, did you log into Sonatype and regenerate credentials in whatever format they now require? There was cutover process a while back that I had to do that was described - I recall getting some email about this that I disregarded until the last minute .
I’ll have a spelunk through my emails and notes tomorrow, but perhaps this will be enough to get you moving in the meantime…
Hi, thanks for your kind words, glad my libraries are useful for you!
I changed back to my old (no expiry) token, and at first it seems progress, because now that token shows up in the usertoken page. But instead of 401, I just got failed upload attempts that ultimately time out with 408.
Then I generated another token, and tried again, and at first it seemed it would time out again, but then it ultimately went on to ‘deployment’ and succeeded
Ah yes, I see this behaviour on release runs every now and then after artefacts have been staged. Not sure if it’s down to server load or maintenance, sometimes the job will complete anyway after a suitably nail biting wait.
.