Publishing fails to release Sonatype repository

[kubukoz]

Version(s)
0.1.18

Describe the bug

Seeing this when trying to publish a library:

Exception in thread "main" java.lang.Exception: java.lang.Exception: Failed to get https://s01.oss.sonatype.org/service/local/staging/profiles/44c2ce0e190826/promote (http status: 500, response: {"errors":[{"id":"*","msg":"Unhandled: Staging repository is already transitioning: orgpolyvariant-1045"}]})

Seeing the failure I checked Nexus and it claimed the repo is closed, so it just needed to be released. I did that manually in the Nexus UI and it seems to have worked.

To Reproduce

Given the nature of publishing it'd be kind of hard to reproduce reliably and independently, but I used this GitHub workflow. The repository at that state also contains the scala-cli config in use.

Expected behaviour
Publishing happens successfully

[kubukoz]

Looks like it worked the second time (hell, it worked for 3 Scala versions in a row!), so that must've been some sort of race condition / temporary quirk. Probably worth looking into, nevertheless

[MartinHH]

This just happened to me as well (Scala CLI version: 1.0.4) when I tried scala-cli publish . --native (from my local machine) with this configuration. I could reproduce this twice (dropped the staging repository and retried), then released manually in the UI (which seems to have worked).

It might be worth noting that between the first failure and the failing retries, I successfully executed scala-cli publish . --js (on first try), so I guess it's not caused by a totally random race condition.

[tgodzik]

@MaciejG604 is doing a PR for coursier publish which might help here https://github.com/coursier/publish/pull/17/files

[MaciejG604]

This should be fixed by #2433 with coursier-publish retrying the staging repository operations on failure.