Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you trying to accomplish?
This is a baby step on the way to Elixir 1.18 (#11295). I've found that the jump of 4 minor versions and a handful of erlang versions is a lot of debugging. I also think that handling the upgrade in smaller steps will lead to a better git history anyways.
Currently we are using Erlang 24 from apt, and there are notes that we should not use ESL for this version of Ubuntu, but times have changed and ESL seems to have caught up. This change re-implements ESL and bumps Erlang to 25.
I think ESL is the best way forward outside of using the RabbitMQ erlang solutions (which I'm fine with doing if desired, I'm just more familiar with ESL).
This also bumps Elixir by a patch version (1.14.4 -> 1.14.5)
The next step in this journey is to bump Elixir to 1.15--this change was primarily to isolate the diff for switching to ESL. The minimum Jammy ESL version ended up being 25.
Checklist