Any expected issues when upgrading to otp 28?

Is it safe to upgrade to otp 28 with the changes to regexes?

5 Replies

AFAIK if there are any issues you'll find out at compile time

Ok, I'll upgrade and see if anything happens.

andyl•2d ago

I had compile errors with erlang 28.0 / elixir 1.18.4-otp-27.
Everything works with erlang 27.2.1 / elixir 1.18.3-otp-27.

ZachDaniel•2d ago

Yep, there are issues with some packages and regexes etc. Please report to the appropriate package maintainers if no one is repsonsive and its a dependency of an Ash project LMK and I'll reach out

frankdugan3•2d ago

I recommend first updating all the Ash packages and doing a mix compile --force, then clean up all the deprecation warnings about the Regexes. The errors you'll get if you just upgrade Erlang to OTP 28 will be hard to debug. I know all of the following are working on OTP 28:

ash                         3.5.13   3.5.13  Up-to-date
ash_ai                      0.1.10   0.1.10  Up-to-date
ash_authentication          4.9.0    4.9.0   Up-to-date
ash_authentication_phoenix  2.7.0    2.7.0   Up-to-date
ash_graphql                 1.7.13   1.7.13  Up-to-date
ash_phoenix                 2.3.5    2.3.5   Up-to-date
ash_postgres                2.6.1    2.6.1   Up-to-date

ash                         3.5.13   3.5.13  Up-to-date
ash_ai                      0.1.10   0.1.10  Up-to-date
ash_authentication          4.9.0    4.9.0   Up-to-date
ash_authentication_phoenix  2.7.0    2.7.0   Up-to-date
ash_graphql                 1.7.13   1.7.13  Up-to-date
ash_phoenix                 2.3.5    2.3.5   Up-to-date
ash_postgres                2.6.1    2.6.1   Up-to-date

Unrelated to Ash, but FWIW mix test.interactive is currently not updated to handle OTP 28. I have an open PR to fix that, it's my last OTP 28 incompatible dep. 🙂

Gaming

Programming

Any expected issues when upgrading to otp 28?

Did you find this page helpful?