Summary
The mix.exs currently specifies elixir: "~> 1.19", but the SDK doesn't appear to use any Elixir 1.19-specific features. Its dependencies (req ~> 0.5, jason ~> 1.4, telemetry ~> 1.2) all work fine on earlier versions.
This means projects on Elixir 1.17 or 1.18 get a version mismatch warning when compiling, even though everything functions correctly.
Proposal
Relax the constraint to elixir: "~> 1.17" (or whatever the actual minimum supported version is). This would widen adoption without any functional changes.
Context
We're using langfuse ~> 0.1.0 in a Phoenix app running Elixir 1.18.4 / OTP 27. The SDK works perfectly — tracing, ingestion, generations all function as expected. The only issue is the compile-time warning:
warning: the dependency :langfuse requires Elixir "~> 1.19" but you are running on v1.18.4
Happy to open a PR if that's preferred. Thanks for the great SDK!
Summary
The
mix.exscurrently specifieselixir: "~> 1.19", but the SDK doesn't appear to use any Elixir 1.19-specific features. Its dependencies (req ~> 0.5,jason ~> 1.4,telemetry ~> 1.2) all work fine on earlier versions.This means projects on Elixir 1.17 or 1.18 get a version mismatch warning when compiling, even though everything functions correctly.
Proposal
Relax the constraint to
elixir: "~> 1.17"(or whatever the actual minimum supported version is). This would widen adoption without any functional changes.Context
We're using
langfuse ~> 0.1.0in a Phoenix app running Elixir 1.18.4 / OTP 27. The SDK works perfectly — tracing, ingestion, generations all function as expected. The only issue is the compile-time warning:Happy to open a PR if that's preferred. Thanks for the great SDK!