Kamil Kloch
Kamil Kloch
As for the version number, I continue to see v1.2.0 in the badge on the top of the README.md, despite https://index.scala-lang.org/typelevel/cats-effect/cats-effect/latest.svg?color=orange correctly pointing to v1.3.0. Github image caching issues?
Should I open this issue in blaze? Update: Never mind, I guess issue can be directly transferred.
Any chance for a 2.12 release?
@ekrich Thanks for pushing the topic. I am using 2.11. The last frontier stopping me from switching to 2.12 ;)
Any news? :)
Any chances for scala 2.11 support?
> Is this matching the behavior described in the breaking changes for munit 1.x? https://github.com/scalameta/munit/releases/tag/v1.0.0-M1 It does indeed.
> But yes, this is the desired behaviour in the v1.0 release line. What is the rationale of such change, if I may ask? Example against such behavior: I would...
Fair point. https://datatracker.ietf.org/doc/html/rfc3986#section-1.1.1 Shall I close the issue?