xerial / sbt-sonatype

A sbt plugin for publishing Scala/Java projects to the Maven central.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[STAGE_FAILURE] Failed to promote the repository

MrPowers opened this issue · comments

Describe the bug

I ran the command to deploy and it errored out. Now I'm trying to bump the version to version 1.1.0 and the old version version that didn't deploy correctly is still causing an error (version 1.0.1). Here's the abbreviated stack trace:

2022-02-08 12:01:39.435-0200 error [SonatypeClient] [promote] Failed  - (SonatypeClient.scala:182)
2022-02-08 12:01:39.435-0200 error [SonatypeClient] Activity name:release, started:2022-02-08T14:01:31.933Z, stopped:2022-02-08T14:01:37.172Z  - (SonatypeClient.scala:458)
2022-02-08 12:01:39.438-0200 error [SonatypeClient]     Failed: RepositoryWritePolicy, failureMessage:Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/com/github/mrpowers/spark-daria_2.12/1.0.1/spark-daria_2.12-1.0.1-javadoc.jar'  - (SonatypeClient.scala:376)
2022-02-08 12:01:39.451-0200 error [Sonatype] [STAGE_FAILURE] Failed to promote the repository.  - (Sonatype.scala:440)

I get this error when running sbt sonatypeRelease.

How to reproduce the issue

Here's the repo. This errors out when running ; + publishSigned; sonatypeBundleRelease.

  • sbt version: 1.4.3
  • sbt-sonatype version: 3.9.10
  • Show your build settings:
$ sbt
> sonatypeProfileName
[info] com.github.mrpowers
> sonatypeRepository
[info] https://oss.sonatype.org/service/local
...

Additional context

I tried running sbt sonatypeClose and that errored out with "java.lang.IllegalStateException: No open repository is found. Run publishSigned first".

sbt sonatypeClean returns "info [SonatypeService] No previous staging repository for [sbt-sonatype] spark-daria 1.0.1 was found - (SonatypeService.scala:99)".

I ran sbt publishSigned and then ran sbt sonatypeClean, but that's still erroring out with "java.lang.IllegalStateException: No staging repository is found. Run publishSigned first".

Any additional suggestions?

Looks like sbt clean was able to fix it 🤦

Sorry for the false alarm!

No worries. It's good your problem was solved.