The recommendation to use Gradle 4.7 only makes sense if you want to use libraries that were published with metadata (https://kotlinlang.org/docs/reference/building-mpp-with-gradle.html#experimental-metadata-publishing-mode) with Gradle 4.7, as later Gradle versions fail to consume those libraries when they read metadata (i.e. when the consumer enables metadata as well). The kotlinx libraries have been published with Gradle 4.7 metadata and, until newer versions get published with a newer Gradle, you need to either keep Gradle metadata disabled on the consumer side or use Gradle 4.7. If you don't use those libraries, then I think you should use the newest Gradle version.
10/13/2018, 4:17 PM
oh, that makes sense, in fact I was having problems with kotlinx using 4.10.2
10/13/2018, 10:21 PM
We had trouble with 4.10 and native dependencies, as described above with metadata. Upgrading would require that to be functional, and republishing all the native libraries we’re using (which, if not ours, are forks because keeping versions compatible is tricky with the recent kotlin dev velocity). We’ll update in the coming weeks as things stabilize. Today, though, 4.7 or no 🎲