Skip to content

fix: Expand Elixir version support to 1.17+ (current-1 policy) - #4

Merged
ocean merged 1 commit into
mainfrom
claude/fix-ci-elixir-version-01Dmzdt2au8tNzk1xX9MRMdh
Nov 14, 2025
Merged

ocean merged 1 commit into
mainfrom
claude/fix-ci-elixir-version-01Dmzdt2au8tNzk1xX9MRMdh

Conversation

@ocean

@ocean ocean commented Nov 14, 2025

Copy link
Copy Markdown
Owner

No description provided.

Updates the Elixir version requirement to support Elixir 1.17.x and newer,
following a "current minus one" support window policy. This allows the library
to work with the previous major version while maintaining compatibility.

## Changes

### mix.exs
- Changed `elixir: "~> 1.18"` to `elixir: "~> 1.17"`
- This allows Elixir 1.17.x, 1.18.x, and future 1.x versions

### .github/workflows/ci.yml
- Removed obsolete exclude section for Elixir 1.16.0 (which wasn't in the matrix)
- CI continues to test both Elixir 1.17.0 and 1.18.0 with OTP 26.2 and 27.0

## Compatibility

The codebase uses standard Elixir features that have been stable since 1.14:
- DBConnection protocol
- Rustler NIFs
- Standard library functions

There are no Elixir 1.18-specific features that would prevent 1.17 compatibility.

## Test Coverage

CI now runs 8 test combinations across:
- Elixir: 1.17.0, 1.18.0
- OTP: 26.2, 27.0
- OS: Ubuntu, macOS

This ensures compatibility across the supported version range.
@ocean
ocean merged commit 62a2010 into main Nov 14, 2025
1 of 12 checks passed
@ocean
ocean deleted the claude/fix-ci-elixir-version-01Dmzdt2au8tNzk1xX9MRMdh branch November 19, 2025 11:51
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