Update CI with current Elixir and Erlang/OTP versions

[nathany-copia]

I am trying to maintain (in CI) the latest 2 major versions, so Elixir 15+ and OTP 25+; wait 2-3 months and it will be Elixir 16+ and OTP 26+

#623 (comment)

This approach runs fewer permutations, so we're not attempting an old version of Elixir on a new version of Erlang. We also can flag the latest version or release candidate as experimental, so that it doesn't block merging, but still reports the failures.

[nathany-copia]

having an entirely separate job just to check code formatting may be overkill?

unless the idea is to continue-on-error for this particular check, but it's not running with a matrix right now anyway 🤔

[yordis]

Pick one matrix (add some attribute to it) to do the formatting and lining and whatnot

[nathany-copia]

Okay. I can give that a try. It's going to be a little tricky to know if I got that right on the first try though, given the "workflow awaiting approval" for testing CI.

1 workflow awaiting approval

[nathany-copia]

Okay. I ran mix format with a newer version of Elixir (as the old lint job was using 1.13)

[nathany-copia]

@yordis @teamon What should be done about all the test failures, even on the "supported" Elixir 1.16 build?

[nathany-copia]

@yordis @teamon Everything should be ready for a re-run in CI.

I've marked Elixir 1.16 as experimental until those test failures are fixed, which I think could be a separate pull request.

[nathany-copia]

I think this should be good to merge now.

Then we can follow-up with a PR to get Elixir 1.16 passing and mark it as no longer "experimental" -- if that sounds okay to you?

[yordis]

Yeah, that works! Remember httparrot is the package that needs to be fixed or replace

[nathany-copia]

Yeah, that works! Remember httparrot is the package that needs to be fixed or replace

Opened #684 for that topic. Let's see if it can be fixed.