Bump coursier version?

[netvl]

Currently sbt-scalafmt-coursier depends on Coursier 1.0.0-RC13, while the latest version is Courser 1.0.0. Because of this, if my build depends both on Coursier 1.0.0 and the latest sbt-scalafmt-coursier, I get the following warnings each time SBT is started:

[warn] Found version conflict(s) in library dependencies; some are suspected to be binary incompatible:
[warn]  * io.get-coursier:coursier-cache_2.12:1.0.0 is selected over 1.0.0-RC13
[warn]      +- io.get-coursier:sbt-shared:1.0.0 (scalaVersion=2.12, sbtVersion=1.0) (depends on 1.0.0)
[warn]      +- io.get-coursier:sbt-coursier:1.0.0 (scalaVersion=2.12, sbtVersion=1.0) (depends on 1.0.0)
[warn]      +- com.lucidchart:sbt-scalafmt-coursier:1.15 (scalaVersion=2.12, sbtVersion=1.0) (depends on 1.0.0-RC13)
[warn]  * io.get-coursier:coursier_2.12:1.0.0 is selected over 1.0.0-RC13
[warn]      +- io.get-coursier:coursier-extra_2.12:1.0.0          (depends on 1.0.0)
[warn]      +- io.get-coursier:sbt-shared:1.0.0 (scalaVersion=2.12, sbtVersion=1.0) (depends on 1.0.0)
[warn]      +- io.get-coursier:sbt-coursier:1.0.0 (scalaVersion=2.12, sbtVersion=1.0) (depends on 1.0.0)
[warn]      +- io.get-coursier:coursier-cache_2.12:1.0.0          (depends on 1.0.0)
[warn]      +- com.lucidchart:sbt-scalafmt-coursier:1.15 (scalaVersion=2.12, sbtVersion=1.0) (depends on 1.0.0-RC13)

This problem is not critical, of course, but a nuisance nevertheless. Is there a particular reason to stick to the prerelease version of Coursier?

[ches]

See #65. I think we just need a maintainer's attention.

[ches]

#65 is merged, just need a release now for these warnings to go away.