Bump sbt-org-policies to 0.7.4

[BenFradet]

It also migrates from cats 0.9.0 to 1.0.0-MF, among other upgrades and enhancements.

[codecov-io]

Codecov Report

Merging #164 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #164   +/-   ##
=======================================
  Coverage   87.62%   87.62%           
=======================================
  Files          40       40           
  Lines         606      606           
  Branches        3        3           
=======================================
  Hits          531      531           
  Misses         75       75

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0ec8322...b5cd021. Read the comment docs.

[juanpedromoreno]

Thanks! This setting would be only for badge purposes. If we want to bump to the latest version of Scalajs, we need to bump up also the sbt-org-policies version: https://github.com/47deg/sbt-org-policies/releases/tag/v0.6.3

[BenFradet]

Thanks, I wasn't entirely sure sbt-org-policies needed to be involved, I'll take care of 47degrees/sbt-org-policies#538 as well then.

[juanpedromoreno]

@BenFradet I needed to upgrade sbt-org-policies and btw I upgraded everything in general: 47degrees/sbt-org-policies#632, including Scalajs.

[BenFradet]

Thanks a lot! I'll bump sbt-org later today 👍

[BenFradet]

mmmh getting https://travis-ci.org/47deg/github4s/jobs/276970366#L846 with 0.6.4 and sbt doesn't launch with 0.7.0

[suhasgaddam]

@BenFradet I think Scala.js 0.6.20 requires sbt 0.13.16.
with
sbt-org-policies:0.7.0
build.properties: sbt.version = 0.13.16

sbt +compile seems to work for me, locally

Links that I stumbled on and for anyone else searching:
https://stackoverflow.com/questions/46206462/java-lang-nosuchmethoderror-sbt-package-zerolsbt-global
http://www.scala-js.org/news/2017/09/01/announcing-scalajs-0.6.20/ -> Breaking Changes

Release notes for sbt 0.13.16:
https://github.com/sbt/sbt/releases/tag/v0.13.16

[suhasgaddam]

The travis ci error: sbt-org-policies:0.6.4 did not have sbt-microsites enabled. We are/were still working on getting sbt-microsites cross-compiling with sbt 1.0.

[BenFradet]

@suhasgaddam thanks! didn't know about the issue with microsites / 0.13.16 min for 0.6.20

[juanpedromoreno]

It should be 0.7.0 0.7.1

[BenFradet]

fixed 😨

[BenFradet]

Weirdly enough it seems to compile fine even though cats.data.Coproduct was removed from cats-1.0.0-MF.

However, it fails during the cats-effect tests with https://travis-ci.org/47deg/github4s/jobs/277197841#L2596.

Still investigating 😕

[BenFradet]

@juanpedromoreno fixed! 👍 Regarding releasing a version, do I just need to edit version.sbt? Should I introduce a specific commit?

[juanpedromoreno]

Yes, you only need to modify the version.sbt.

Are we releasing the 0.1.5.1 or 0.16.0? As it's not binary compatible I propose 0.16.0, what do you think?

Either way, I'd suggest doing it in a different PR, since due to 47degrees/sbt-org-policies#637, the plugin is not running the release task correctly. Hence, we might need to edit the orgAfterSuccessCI task by something like this https://github.com/47deg/sbt-org-policies/blob/2c89b98d9366b626a978e3ff17cbc25e561ea48b/.travis.yml#L31-L44, in the .travis.yml file.

[juanpedromoreno]

This is really great, outstanding work.

[BenFradet]

@juanpedromoreno ok thanks 👍 , I'll open a new PR

yes, I agree that 0.16.0 makes more sense btw