Is there a non milestone version of 0.8.0?

[xuanli09]

Right now we're using circe-generic and core at 0.8.0, but circe-derivation on 0.8.0-M2. This mixture helped us with our compile time quite a bit.

Just wondering if 0.8.0 will be published, so we can sync our versions together in our build. It looks like this project already has a 0.9.0-M1 branch.

[travisbrown]

We are using circe-derivation 0.8.0-M2 in several projects at Stripe, so personally at least I consider it production-ready, and the changes I have in the pipeline should be entirely source-compatible with current usage.

I've not been planning to release a non-milestone version for 0.8, since I'm still working on what I think should be the final non-milestone version of the API and functionality, and since circe 0.9.0 is just around the corner. If it would be particularly useful for people, I'd consider publishing both an 0.8.0 and 0.9.0 at some point next week, but otherwise I'll probably just publish a milestone for 0.9 once 0.9.0 final is out.

[EdgeCaseBerg]

If it would be particularly useful for people

I would appreciate if 0.8.0 could be released!

I do something like this in my build right now:

libraryDependencies ++= Seq(
  "io.circe" %% "circe-core",
  // "io.circe" %% "circe-generic", // Use derivation instead which has no 0.8.0 version, only milestones
  "io.circe" %% "circe-parser",
  "io.circe" %% "circe-java8"
).map(_ % circeVersion)

libraryDependencies ++= Seq(
  "io.circe" %% "circe-derivation" % "0.8.0-M2",

and it'd be nice to not have to

[travisbrown]

@EdgeCaseBerg Sorry for the long delay in responding, but matching up patch versions between the "core" circe modules (i.e. the ones in the main repo) and the rest isn't a goal for the project—see e.g. the discussion here.

[aparo]

I suppose that this issue can be close.