The artifacts of the core of Scala.js 1.0.0 are now on their way to Maven Central. It will still take several days before all the next-to-core satellite projects are published, and it could be weeks until we actually properly announce this release.
Until the official announcement, I ask you not to make any fuss about it. You are encouraged to publish your libraries for Scala.js 1 when possible (refer to the release notes of 1.0.0-RC2), but otherwise please don’t go everywhere shouting out it’s arrived.
The following satellite projects that we maintain have now been published for Scala.js 1.0.0:
The ones that are mentioned in the release notes of 1.x to replace features that were previously in the core: scalajs-cli, scalajs-env-phantomjs, scalajs-env-jsdom-nodejs, scalajs-env-selenium and jsdependencies 1.0.0
The following libraries have been published for Scala.js 1.0.0:
com.lihaoyi::utest::0.7.4
com.lihaoyi::sourcecode::0.2.1
com.lihaoyi::geny::0.5.1
com.lihaoyi::castor::0.1.2
com.lihaoyi::fansi::0.2.9
com.lihaoyi::scalatags::0.8.5
com.lihaoyi::pprint::0.5.9
com.lihaoyi::fastparse::2.2.4
Currently blocked on org.scala-lang.modules::scala-collection-compat. @sjrd any idea who can publish a new version of that? Once that is out, I’ll be able to publish com.lihaoyi::upickle, and that will be it for me
Once scala-collection-compat and scalacheck are available on the Maven central, I can release Airframe and AirSpec testing framework for Scala.js 1.0.0 https://github.com/wvlet/airframe/pull/926
I’m not seeing org.scala-lang.modules:scala-collection-compat_2.12:2.1.4 on https://search.maven.org/search?q=scala-collection-compat, although the 2.11 and 2.13 versions appear to be present.
Not sure if just sonatype sync slowness or something else; will check back later today after work
I’m still not seeing the artifact for org.scala-lang.modules:scala-collection-compat_2.12:2.1.4 on maven central. Are we sure it made it up there? All the other cross versions appear to be present
Kudos to Rickard Nilsson for granting merge and publishing authority to a set of maintainers that now includes Aaron Hawley, Daniel Spiewak, and Erik Osheim. (And myself, though mostly as a backup in case we run short.)
?