RepoJournal
Elixir & Phoenix Elixir & Phoenix
138 wires and counting

$ follow Elixir & Phoenix

Keep up with Elixir & Phoenix in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-09-26
stories 27

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Phoenix regenerates Chrome-loadable certs, LiveView handles dangling asset symlinks

By RepoJournal · Filed · About Elixir & Phoenix · Composed from the cited sources · methodology

A cert-generation regression that broke Chrome handshakes on dev servers and a LiveView fix for dangling colocated-asset symlinks are the day's real reader-facing work, with the rest of the wire cleanup and CI plumbing.

Restore NULL parameters on phx.gen.cert's public key algorithm (#6848) phoenixframework/phoenix

by Gaurav Vijay Jadhav

PR #6332 dropped `parameters: :NULL` from the signature and public key algorithm identifiers, and Chrome's BoringSSL aborts the handshake on the resulting cert with `ERR_SSL_PROTOCOL_ERROR` while curl and OpenSSL accept it, so dev servers worked everywhere except the browser you were using. The parameters field is restored per RFC 3279 2.3.1 requirement that `rsaEncryption`'s field be present a...

Handle outdated or dangling symlinks for colocated assets phoenixframework/phoenix_live_view

by SteffenDE

Colocated assets whose symlinks are outdated or dangling no longer trip up the compiler, closing an issue that had been open since #4447 and related to #4305 and #4347. This is the LiveView side of the asset pipeline work SteffenDE has been running this week.

Handle file reader upload errors phoenixframework/phoenix_live_view

by lukaszsamson

`readNextChunk` only assigned `reader.onload`, and since that event fires only on success the `e.target.error !== null` check was dead code: a failed chunk read fired no callback at all, so `this.error()` was never reached and the upload hung instead of surfacing a failure. File readers now handle their error path.

Fix async close leaking to replaced transport phoenixframework/phoenix

by SteffenDE

An async close was leaking through to a transport that had already been replaced, the failure tracked as #6852. SteffenDE's fix keeps the close on the transport it was issued against.

Keep :erts in release applications without colliding with the ERTS copy elixir-lang/elixir

by rgfaber

Releases listing `:erts` in their applications, which happens indirectly through a dependency on horus, used by khepri, fail with `Unknown application :erts`. A commit for #14236 removed `:erts` from `release.applications` while leaving it in the boot modes, and the underlying collision dispatched the `:erts` application to the ERTS copy step, running `copy_erts/1` twice concurrently.

Quick answers

What shipped in Elixir & Phoenix on September 26, 2026?
A cert-generation regression that broke Chrome handshakes on dev servers and a LiveView fix for dangling colocated-asset symlinks are the day's real reader-facing work, with the rest of the wire cleanup and CI plumbing. In total, 15 commits, 11 pull requests, and 1 releases landed.
Who contributed to Elixir & Phoenix on September 26, 2026?
6 developers shipped this update, including rgfaber, preciz, rhcarvalho, Gaurav Vijay Jadhav, SteffenDE, and lukaszsamson.
What were the notable Elixir & Phoenix updates?
Restore NULL parameters on phx.gen.cert's public key algorithm (#6848), Handle outdated or dangling symlinks for colocated assets, and Handle file reader upload errors.