Qqwy
Hey everone! Recently I’ve started updating the dependencies of my Elixir packages, to ensure they all are up-to-date. Some of these were still written in the time of Elixir v1.2.x.
Currently, we are of course at version 1.8.1.
So here are two question to you, dear community:
-
Are you still stuck on older Elixir versions? If so, why and which one(s)?
-
When building a library, what versions of Elixir should be supported at least? Is it okay to only support the latest Elixir version? If not, how long should we keep supporting earlier versions? Or should we strive to, if at all possible, support all earlier versions?
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
hauleth
In general I support the version from time I have created library and do not update minimal version as long as it do not interfere with what I am trying to do. It would be helpful though if there would be a tool to detect minimal supported version which I could add to my CI pipeline to prevent versions mismatches.
Qqwy
in Travis you can run your test suite on many different Elixir versions.
This is how I found out that I am now, while upgrading dependencies, often no longer able to support elixir v1.2 (but I personally think that that version is now old enough to leave behind).
Currently, my plain test
.travis.ymlconfiguration looks like this:PragTob
A lot of libraries seem to only support the last 3 minors (so 1.6 1.7 and 1.8). Upgrades of elixir versions are usually very easy so I think that’s fine. Iirc the formatter was also introduced in 1.6 so that was a huge leap. I also see a lot of libraries that require OTP 20+ or 19+ (esp. Dev tooling related ones). From that point 1.6+ seems reasonable. Phoenix currently supports 1.4 but the new version seems to require 1.5.1+ so that seems safe to support (assuming a lot of users need Phoenix)
I’m a big fan though of taking semver seriously which means not dropping support without a major version release - most libraries don’t seem to honor that but with the easy upgrade path I can see why.
I haven’t heard of people being stuck on old elixir versions but having data would be nice. Maybe hex could optionally get data about the elixir versions its clients run?
kip
I’ve kept support at elixir 1.5 so far. But it’s gettingk harder since lots of good additions to Calendar and Date in 1.8 make me think about a big bump. Elixir upgrades tend to be very straight forward I’m finding it harder to justify back more than maybe two minor release.
It’s a great question though and I’m curious what other lib Writers do too.