Cats: publish for 2.13.0-M3

Created on 4 May 2017  路  26Comments  路  Source: typelevel/cats

although it's still early in the 2.13 cycle, cats is an enabler for many other projects, so having 2.13 compatibility work progressing, and artifacts published if possible, would be good

in progress

Most helpful comment

Scala 2.13.0-M3 is out.

(With M3 just out, and with the big push to Cats 1.0 now complete 馃帀, perhaps this would be an opportune time for someone to revisit this...)

All 26 comments

馃憤 Several upstream dependencies need to be published first.

[warn] :: org.typelevel#discipline_2.13.0-M1;0.7.2: not found
[warn] :: org.typelevel#catalysts-platform_2.13.0-M1;0.0.5: not found
[warn] :: org.typelevel#catalysts-macros_2.13.0-M1;0.0.5: not found
[warn] :: org.scalatest#scalatest_2.13.0-M1;3.0.0: not found

ScalaTest 3.0.3 is available for 2.13.0-M1 (as shown on https://github.com/scala/make-release-notes/blob/2.13.x/projects-2.13.md)

kind-projector is available now (0.9.4), which I think was one of the blockers here

Last remaining issues:

  • [ ] Catalysts (https://github.com/typelevel/catalysts/issues/14)

    • [ ] sbt-catalysts (https://github.com/typelevel/sbt-catalysts/pull/30)

  • [x] Simulacrum (https://github.com/mpilquist/simulacrum/pull/81)
  • [x] Discipline (https://github.com/typelevel/discipline/issues/32)
  • [x] ScalaTest for Scala.JS (https://github.com/scalatest/scalatest/issues/1152)

    • [x] Depends on ScalaCheck for Scala.JS (https://github.com/rickynils/scalacheck/issues/330)

I'll push a series/0.9.x branch once the above are resolved, which can then be published. How exactly does our artifact publication work? Do we tag and let the CI do it? Or do we manually cut releases?

thanks Daniel for your attention to this, much appreciated

Simulacrum 0.11.0 is released.

fyi, catalysts (and so would cats) requires tut 0.5.x

I've got a feeling scoverage will block this, too.

fyi, tut is released. For scoverage, see https://github.com/scoverage/scalac-scoverage-plugin/issues/205

So scala-logging is needed for scoverage - https://github.com/typesafehub/scala-logging/pull/94

Once the above PR's are merged, I can release catalysts with a workaround for scoverage if it is still not finally resolved. At that point I can also PR the few, small changes that are needed to build 2.13.0-M1, including the scoverage workaround.

For 2.13.0-M1 we are also waiting for a new release of sbt-microsites to pull in tut 0.5.3.

Just recently found that tut 0.5.3 uses an older version of scala-xml so best is if that were done first.

I have catalysts compiling fine on 2.13.0-M1, it's by doing that first that I'm finding the other issues first

Scala 2.13.0-M3 is out.

(With M3 just out, and with the big push to Cats 1.0 now complete 馃帀, perhaps this would be an opportune time for someone to revisit this...)

https://github.com/typelevel/catalysts/issues/14#issuecomment-362104625

Links to the bulk of the work I did last year. I will revisit this on Friday, if thats OK.

in the context of 2.13 community build, I'm finding that all dependencies (catalysts, discipline, simulacrum, ScalaTest, ScalaCheck) are building fine, so it's just cats that doesn't compile yet

@SethTisue I think we need to upgrade Machinist to M3, before we can build cats.

the action's over at #2173 now

removed the milestone since the #2173 is already in 1.1 milestone (although if it doesn't get unblocked soonish it might get delayed to the next release)

What about -M4 ?..

the M4 ticket is https://github.com/typelevel/cats/issues/2267

closing this one since M3 is obsolete.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

LukaJCB picture LukaJCB  路  4Comments

fosskers picture fosskers  路  3Comments

mcanlas picture mcanlas  路  4Comments

davidabrahams picture davidabrahams  路  3Comments

tg44 picture tg44  路  4Comments