Update circe version for publishing enumeratum-circe on 2.13 (jvm+js)

[zakpatterson]

Hi, I noticed that enumeratum_circe has not published on 2.13 yet. Circe is available for 2.13 via 0.12.0-M4. Tests pass on this version without modification.

[coveralls]

Coverage remained the same at 91.313% when pulling 85b0658 on zakpatterson:update-enumeratum-circe_2.13 into fabfd5a on lloydmeta:master.

[zakpatterson]

This works for the jvm project, but not js. I'm not super experienced on the js side yet, so that'd be better left to someone that knows how to fix whatever issue is coming up there.

[lloydmeta]

I'm following up with this on the Circe side to see why it fails with ScalaJS.

[lloydmeta]

Travis Brown answered my question in circe/circe#945 (comment)

Basically 0.12 w/ ScalaJS requires you to bring your own java.time._ implementation (in release notes)

So I think this just needs something like the following

.jsSettings(
  libraryDependencies += "io.circe" %%% "not-java-time" % "0.2.0" % Test
)

added to the end of the enumeratumCirce module definition:

enumeratum/build.sbt

Lines 316 to 331 in fabfd5a

	lazy val enumeratumCirce = crossProject(JSPlatform, JVMPlatform)
	.crossType(CrossType.Pure)
	.in(file("enumeratum-circe"))
	.settings(commonWithPublishSettings: _*)
	.settings(testSettings: _*)
	.settings(
	name := "enumeratum-circe",
	version := "1.5.22-SNAPSHOT",
	crossScalaVersions := scalaVersionsAll,
	libraryDependencies ++= {
	Seq(
	"com.beachape" %%% "enumeratum" % Versions.Core.stable,
	"io.circe" %%% "circe-core" % theCirceVersion(scalaVersion.value)
	)
	}
	)

[zakpatterson]

Thanks for the research @lloydmeta, I went ahead and added your suggestion, but filtered to only modify for 2.13.

[zakpatterson]

I just retriggered the build via a force-push with no modifications. I'm not sure what caused the prior 2.10 testing error. Looks like this works.

[lloydmeta]

Thanks ! LGTM.

[lloydmeta]

Just released a 2.13 enumeratum-circe with this change :)