-
Notifications
You must be signed in to change notification settings - Fork 59
Support OTP 28 #466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support OTP 28 #466
Conversation
Tentatively assigning this to 4.2.0. |
0b74657
to
03b7702
Compare
https://hex.pm/packages/katana_code/2.4.0 is ready 💪🏻 |
Here it comes 😄... lemme see how fast I can do this. And by "fast" I don't mean sloppy, I mean "easy"... |
03b7702
to
f782978
Compare
Feel free to release at whatever moment, no pressure. If you end up having this in 4.1.0 do adjust the milestone here and in the linked issue. |
Hm... this is failing for |
This is now waiting for e.g. 2.4.1 from |
https://hex.pm/packages/katana_code/2.4.1 is here :) |
And this is now updated and being tested. |
I think we're getting bit by this: erlang/rebar3#2954. Good news: there seems to be a fix on the way... I'll move this to 4.2.0, so we have more time to fix it. |
Well… CI worked in all the required ones… I'll merge this PR. We can upgrade rebar3 in the next one :) |
Oh, Ok, I thought the required and CI range was similar. In any case, if rebar3 doesn't go 3.26 but e.g. 3.25.1 we'll get the CI update automatically given how |
Description
There's a few assumptions here, but since I wanna split this from #463, I'm doing it already.
Further considerations
This most likely required inaka/katana-code#91 being accepted, merged and released (for later import here).