Skip to content

chore: upgrade toolchain to latest Elixir/Erlang/Rust#12

Merged
fahchen merged 1 commit into
mainfrom
chore/bump-toolchain-latest
Jun 28, 2026
Merged

chore: upgrade toolchain to latest Elixir/Erlang/Rust#12
fahchen merged 1 commit into
mainfrom
chore/bump-toolchain-latest

Conversation

@fahchen

@fahchen fahchen commented Jun 28, 2026

Copy link
Copy Markdown
Owner

Summary

  • Bump .tool-versions to Elixir 1.20.0 / OTP 29.0 / Rust 1.93.1.
  • Update CI matrix-test to the three latest Elixir/OTP pairs (1.20.0/29.0, 1.19.5/28.4, 1.18.4/27.3.4.4); drop EOL 1.16/1.17 & OTP 26.
  • Remove an unused require Logger newly flagged by Elixir 1.20's unused-require warning.

Why

The v0.7.0 hex publish failed: the Publish job's precompiled-NIF download from the GitHub release CDN hit an OTP :ssl key_usage_mismatch fatal alert. This is the OTP 27.1.3–27.2 regression (erlang/otp#9208, fixed by #9286). The repo was pinned to OTP 27.2 — squarely in the broken window. Moving to OTP 29 resolves it.

Test plan

  • mix compile --warnings-as-errors clean on Elixir 1.20.0 / OTP 29.0
  • mix test → 142 passed, 1 skipped on Elixir 1.20.0 / OTP 29.0
  • CI matrix green across all three pairs

🤖 Generated with Claude Code

Bump .tool-versions to Elixir 1.20.0 / OTP 29.0 / Rust 1.93.1 and update
the CI test matrix to the three latest Elixir/OTP pairs.

OTP 29 also resolves the ssl key_usage_mismatch regression
(erlang/otp#9208, fixed by #9286) present in OTP 27.1.3-27.2, which
broke precompiled-NIF downloads from the GitHub release CDN during
`mix hex.publish`.

Remove an unused `require Logger` newly flagged by Elixir 1.20's
unused-require warning.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@fahchen
fahchen merged commit cbbe8c8 into main Jun 28, 2026
7 checks passed
@fahchen
fahchen deleted the chore/bump-toolchain-latest branch June 28, 2026 06:50
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.

1 participant