-
Notifications
You must be signed in to change notification settings - Fork 88
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
roll an 0.3.0 release #180
Comments
tagged, release notes attached: https://github.com/scala/scala-collection-compat/releases/tag/v0.2.2 |
Travis publishing run: https://travis-ci.org/scala/scala-collection-compat/builds/490341153 |
the new JDK 11 jobs failed but that's fine, we want to publish from 8. e71dc97 should fix it for next time |
the 6 staging repos on oss.sonatype.org are orgscala-lang-1664 through orgscala-lang-1669. I hit "close" and "release" on them
|
gah, 2.11 artifacts aren't on Maven Central: https://repo1.maven.org/maven2/org/scala-lang/modules/scala-collection-compat_2.11/0.2.2/ |
haha well no wonder, wtf
|
I'm rolling 0.3.0. no code changes, but I want to verify that the full cross-publish goes smoothly, and @julienrf pointed out that although we aren't guaranteeing bincompat yet (that's #162), 0.2.2 wasn't bincompat with 0.2.1. seems better to bump the version number to 0.3.0 to give more indication that bincompat broke. |
This comment has been minimized.
This comment has been minimized.
gah, what a mess. I fixed the JDK 11 jobs to be green, green is good, but those jobs are also uploading artifacts to the staging repos, which we don't want. 😖 |
steps:
|
needed over at scala/community-build#849
The text was updated successfully, but these errors were encountered: