Phoenix 1.8.11

Remember when Phoenix 1.0 shipped in 2015 with little more than channels, a router, and a dream? Eleven years later, the framework is deep into its 1.8 line, shipping steady patch releases that keep the Elixir web story moving. The latest chapter: Phoenix 1.8.11, released August 12, 2026 — one day after 1.8.10, and it exists to fix one specific crash.

The Fix That Matters

Phoenix 1.8.11 resolves an issue where the framework could crash on boot if Mix was available but not started (#6789). For anyone running Phoenix inside custom release tooling or unusual boot environments, this is the difference between a clean start and a stack trace.

The Road Through 1.8.10

Just a day earlier, 1.8.10 delivered a broader set of improvements that 1.8.11 builds on:

• Fixed spurious "must restart your server" messages from the code reloader when compile.lock mtime changed without a content change.
• Added missing websocket options to Phoenix.Endpoint.
• phoenix.js now closes and retries the longpoll transport when a batch POST times out, and releases stale reply bindings of buffered pushes.
• Phoenix.Router now supports plugs with options in pipe_through.
• phx.gen.release --docker uses the Bob API to find Docker images.
• LongPoll transport tokens can be sent in a header — with a note that this behavior changes in 1.9.

What's Next

The 1.8 line continues its role as the stable, boring-in-the-best-way backbone of the Elixir ecosystem, while the LongPoll header change quietly points toward 1.9. Upgrade when you can — the boot fix alone is worth it.