Skip to content
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

Release 0.6.2 #454

Closed
wants to merge 2 commits into from
Closed

Conversation

dwijnand
Copy link
Collaborator

@dwijnand dwijnand commented Feb 2, 2020

Release checklist

@dwijnand dwijnand added this to the 0.6.2 milestone Feb 2, 2020
@dwijnand dwijnand self-assigned this Feb 2, 2020
@dwijnand
Copy link
Collaborator Author

dwijnand commented Feb 3, 2020

not found: https://repo1.maven.org/maven2/com/typesafe/mima-core_2.12/0.6.2+1-1dcaf4a5+20200202-2309/mima-core_2.12-0.6.2+1-1dcaf4a5+20200202-2309.pom

I made the change e782134 and changed the local version of the sbt-plugin and re-published. The mistake was that that published a manifest using the sha-tagged version of mima-core.


So I just deleted the 0.6.1 release of sbt-mima-plugin in bintray, to re-re-release with that fixed, and now I'm getting

[error] (sbtplugin / publishSigned) error uploading to com.typesafe/sbt-mima-plugin/scala_2.12/sbt_1.0/0.6.2/docs/sbt-mima-plugin-javadoc.jar: {"message":"Unable to upload files: An artifact with the path 'com.typesafe/sbt-mima-plugin/scala_2.12/sbt_1.0/0.6.2/docs/sbt-mima-plugin-javadoc.jar' already exists"}

So I guess 0.6.2 is just DOA now.

@dwijnand dwijnand closed this Feb 3, 2020
@dwijnand dwijnand deleted the update/mima-0.6.2 branch February 3, 2020 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

1 participant