Kotlin minimum 1.4.30, coroutines 1.4.3 #34
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jvz I'm wondering if we should go directly to 1.6? Being two versions behind stable is not unreasonable. Or 1.5 alternatively. |
Closed
|
I'd like to make a release of 1.3.0 without Kotlin 1.4 first, then 1.4.0 with Kotlin 1.4, then we can also update the baseline version requirement for a 1.5.0 release (could even match the Kotlin versions along the way like that). Now that the build has been more automated, cutting releases should be much easier (I've just been a little busy at work this month). |
|
@jvz Ping on releasing 1.3.0? Or should we bother at this point? Kotlin is at 1.9.x now. We could probably skip to 1.7 without causing any undue issues. |
|
Closing in favor of #43 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #31.