A modern programming language that makes developers happier.

kotlinlang

_Probably not the right place, but wanted to start somewhere._
I imagine an alternate universe where Kotlin versions follow semantic versioning in `&lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;` form so updates could be automated by scripts (Renovatebot/dependeabot) with ease. The current `1.&lt;major&gt;.&lt;minor&gt;&lt;patch&gt;` format is hard to parse and also not even correct since theoretically there was no major breaking change yet (that is if you ignore the deprecated/removed methods, renamed command line flags, incubation/optin features, compiler backend change, Gradle DSL changes, and tons of warnings etc.). Is there a proposal for doing the "Java maneuver" and going from 1.6 to 7.0 next release?

<https://youtrack.jetbrains.com/issue/KT-44136/Standardize-the-versioning-scheme#focus=Comments-27-4620058.0-0>

cheers!, can't believe it only has 2 upvotes :cry:

<@U011UDDFMCL> upvote the YT issue :wink:

FWIW, kotlin-stdlib-jvm *is* meant to be semver-compatible as far as A*B*I goes (deprecations/removals do change A*P*I though). the compiler isn't under any stability guarantees, and I believe CLI and Gradle DSL aren't either, even in patch versions.