You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The need for the backwards compatibility tests is detailed here: #289
Conaider adding tests for forward compatibility. That is, publish kx-benchmark plugin and runtime with an older Kotlin and use it in a project that uses a newer (minor or major) Kotlin version. This would guarantee that kx-benchmark remain compatible with the newest Kotlin versions.
This would also validate the statement like "ensure you're using Kotlin 2.0.0 or newer" in the README.
The text was updated successfully, but these errors were encountered:
The need for the backwards compatibility tests is detailed here: #289
Conaider adding tests for forward compatibility. That is, publish kx-benchmark plugin and runtime with an older Kotlin and use it in a project that uses a newer (minor or major) Kotlin version. This would guarantee that kx-benchmark remain compatible with the newest Kotlin versions.
This would also validate the statement like "ensure you're using Kotlin 2.0.0 or newer" in the README.
The text was updated successfully, but these errors were encountered: