-
Notifications
You must be signed in to change notification settings - Fork 87
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 2.4.0 #413
Comments
Is there any ETA for this release? |
If I don't get to it today, then early next week. |
@SethTisue Cool, thank you! 🙏 |
the 3.0.0-M2 artifacts haven't shown up on Maven Central, but the others have. hopefully it's just that some extra patience is needed... |
Is it possible that just because of some change from
|
Working for JVM and JS 2.11 - 3.0.0-M3 (no M2) and Native 2.11 - 2.13 for |
@sideeffffect presumably related to #417 — please open a ticket with details: what Scala version(s) are affected, whether it happens on JVM or JS or Native or all three, whether use of silencer might be a factor, etc etc, and we'll figure it out |
Would it be possible to also publish 2.4.0 for scala js 0.6? |
@jodersky hmm, well I'd honestly really rather not. at least not unless it's creating some kind of serious roadblock for actual 0.6 users. is there a real need for 0.6 users not to just leave the dependency frozen at whatever version they're already on? most of the repos I'm involved with dropped 0.6 support a while ago |
It's not a huge problem, but for projects that cross-build, it does make the build matrix much more complex. The reason I asked was for unblocking com-lihaoyi/upickle#330, but in the end we were able to drop the dependency on scala-collection-compat altogether, so it's not an issue there anymore. |
nope. Sonatype just.... disappeared them, like mobsters disappearing a murder witness or maybe I'm jumping to conclusions and there is somehow something wrong in the build? https://repo1.maven.org/maven2/org/scala-lang/modules/scala-collection-compat_sjs1_3.0.0-M2/2.4.0/ is also missing over at https://travis-ci.com/github/scala/scala-collection-compat/builds/214738364 , I hit restart on both M2 jobs, which should make them publish again, to new staging repos new logs:
aha! the jobs say M2 on them, but the artifacts say M3. I apologize to the Sonatype-American community. let's take a closer look at https://travis-ci.com/github/scala/scala-collection-compat/jobs/476713037 it does have but then so I guess this has something to do with the weird way this repo is set up (#395 is where we complain about that) and aha, okay, I'll PR a fix |
#420 🌿 |
Because publishing is weird in this repo, I don't trust myself to attempt to back-publish, and anyway I want to be sure that full publishing is still working. So I'm going to roll 2.4.1: #422 |
Motivations:
@nowarn
(Update 2.12's scala.annotation.nowarn once 2.12.13 is out #397, make@nowarn
a ClassfileAnnotation, as in 2.12.13 #417)Steps:
The text was updated successfully, but these errors were encountered: