Discovered an issue introduced in 1.6.20-M1, anyon...
# javascriptm
Michael Friend
04/01/2022, 7:28 PMDiscovered an issue introduced in 1.6.20-M1, anyone else run into this yet? Wanted to makes sure it wasn’t a duplicate https://youtrack.jetbrains.com/issue/KT-51802
k
Karel Petránek
04/01/2022, 8:02 PMHey, I think it is this issue: https://youtrack.jetbrains.com/issue/KT-50504. It has been fixed a few days ago so the final 1.6.20 should be good to go.
👏 1
m
Michael Friend
04/01/2022, 8:07 PMah yes looks like thats the same issue, thanks for the find! Will close mine as duplicate
Michael Friend
04/01/2022, 8:54 PMOof just noticed the fix version is 1.7.0. hopefully it'll actually make it into 1.6.20, or at least .21
k
Karel Petránek
04/01/2022, 9:51 PMI think this will break any bigger project, hopefully it will get into 1.6.20
j
jw
04/02/2022, 12:01 AM1.6.20 is already out
m
Michael Friend
04/02/2022, 12:22 AMOut of release candidate? Is it just up on maven but not officially announced yet?
j
jw
04/02/2022, 3:11 AMyep. so hopefully .21
🤞 1
m
Michael Friend
04/04/2022, 9:11 PMFYI the ticket was reopened to backport for 1.6.21
🎉 2
b
bashor
04/08/2022, 3:46 PMThe fix is backported to 1.6.21, kudos to @Ilya Goncharov [JB]
🙏 2
m
Michael Friend
04/08/2022, 3:58 PMThanks @Ilya Goncharov [JB]!
Michael Friend
04/20/2022, 2:41 PM1.6.21 released this morning and fixes this issue 🎉 Thanks again to the JB team for getting this done
🎉 1
3 Views