<@U05N94LDU79> is there any chance we can get the ...

# arrow-contributors

[Kev]

@Alejandro Serrano.Mena is there any chance we can get the core-high-arity fix into a 1.x release?

[Alejandro Serrano.Mena]

it would involve a significant time investment, because now main targets 2.0

[Alejandro Serrano.Mena]

would it be a good solution for you to wait until Kotlin 2.1.0-RC is out, and if the fix that blocks our release is fixed, depend on Arrow 2.0-Beta1 instead?

[Kev]

I thought as much. I’ll wait for the 2.1.0 release and copy the methods I need in the meanwhile. Thanks for the response

[Alejandro Serrano.Mena]

thanks for your understanding 🙏

[Alejandro Serrano.Mena]

may I ask you to check if 2.0.0-beta.1 fixes your problem?

[Kev]

I have not - will take a look over the weekend

[Alejandro Serrano.Mena]

please check with 2.0.0-beta.2 if possible, so we know that the behavior applies to the latest release

[Kev]

Can this be used in place of 1.1.4 without breaking changes?

[Kev]

And will these require Kotlin 2.x?

[Alejandro Serrano.Mena]

in principle we do not guarantee not breaking code unless you use 1.2.x and remove all the uses of deprecated functions

[Kev]

Quick test, it works. Thanks!

[Kev]

Any idea when 2.0.0 will officially be released?

[Alejandro Serrano.Mena]

the plan is to do it right after Kotlin 2.1.0 is released and KSP is updated for it, we think that should be around the first week of December