Arrow: Enforce Kotlin and Coroutine release version when releasing Arrow

[raulraja]

Ensure Kotlin version and coroutines version only point to released versions as part of the Arrow release. In 0.8.0 we released depending on RC builds and that should never happen.

[alissonfpmorais]

I want to take this one!

[pakoito]

What's the plan? I don't know how to enforce it!

[raulraja]

I think as a rule of thumb Arrow has to go with the standard lib kotlin version release, so it should be enough to get the latest version value in maven central releases and ensure we are not behind. This is mostly a CI task to make sure we are not releasing without updating to the latest stable std lib version.

[pakoito]

There's a plugin that checks whether you're in the latest version of your dependencies. Maybe run that on a git hook or something?

[alissonfpmorais]

My plan is create a Gradle task using same plugin already used by arrow, gradle-versions-plugin from ben-manes and call this task on travis whenever a new release is deployed. If dependency version is correct then build pass, otherwise fails. What do you think?