Skip to content
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

Officially support Elixir 1.18 #1033

Merged
merged 7 commits into from
Jan 7, 2025
Merged

Officially support Elixir 1.18 #1033

merged 7 commits into from
Jan 7, 2025

Conversation

fhunleth
Copy link
Member

Most libraries appear to work just fine with Elixir 1.18 and Nerves, so
remove the warning when building.

@fhunleth
Copy link
Member Author

Oh, wow, there's a nontrivial CI failure. I'll get to fixing that!

@fhunleth fhunleth force-pushed the support-elixir-1.18 branch from 81a44bf to a83fe2b Compare December 19, 2024 19:40
@fhunleth fhunleth force-pushed the support-elixir-1.18 branch from a83fe2b to 212fad6 Compare January 6, 2025 17:57
Most libraries appear to work just fine with Elixir 1.18 and Nerves, so
remove the warning when building.
@fhunleth fhunleth force-pushed the support-elixir-1.18 branch from 212fad6 to 3c0e041 Compare January 6, 2025 22:30
It broke due to the new JSON.Encoder protocol, but it's not too hard of
a fix.
@fhunleth
Copy link
Member Author

fhunleth commented Jan 7, 2025

Tests and Dialyzer pass now. The tests are a little on the flaky side, but I think that's been the case for a while. In any case, I don't think anything substantial has changed, and Elixir 1.18 has been working well for me in my usage.

@fhunleth fhunleth merged commit 65d486c into main Jan 7, 2025
4 of 6 checks passed
@fhunleth fhunleth deleted the support-elixir-1.18 branch January 7, 2025 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants