RepoJournal
Elixir & Phoenix Elixir & Phoenix
107 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-07-04
stories 9
RSS Archive Reviews Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

PHOENIX TIGHTENS LONGPOLL SECURITY WHILE ELIXIR FIXES SPEC BUGS ACROSS THE STACK

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

SteffenDE Gigitsu pnezis
3 people shipped this
SteffenDE @SteffenDE 1 cited Gigitsu @Gigitsu 1 cited pnezis @pnezis 1 cited

Phoenix is enforcing a hard cap on longpoll batch sizes to close a potential attack surface, and you need to know the upgrade path.

Phoenix shipped a breaking change that enforces a maximum of 100 entries per longpoll request [1], hardening against a known attack vector. The client has enforced this limit since 1.8.6, so if you're running older versions with heavy longpoll traffic, upgrade to 1.8.6 or 1.8.7 first before jumping to the latest. On the auth front, Phoenix now lets authToken be a function instead of a static value [2], giving you a cleaner path to refresh tokens on reconnect without mutating the socket directly. Meanwhile, Elixir fixed a spec bug in File.copy/3 [4] that was incorrectly excluding 0 as a valid return value, and Ecto patched wrong placeholder numbering when using fragment sources with schemas [3], a subtle bug that would break parameterized queries in edge cases.

$ ls elixir/reviews/ # the step-back reads

the week in review Comments land in the Elixir AST the month in review Elixir core tuning, Ecto breaking change, LiveView patches dominate August
Topics: Elixir & Phoenix Full archive → Weekly reviews →

Quick answers

What shipped in Elixir & Phoenix on July 4, 2026?
Phoenix is enforcing a hard cap on longpoll batch sizes to close a potential attack surface, and you need to know the upgrade path. In total, 6 commits and 3 pull requests landed.
Who contributed to Elixir & Phoenix on July 4, 2026?
3 developers shipped this update, including SteffenDE, Gigitsu, and pnezis.
What were the notable Elixir & Phoenix updates?
Enforce longpoll batch size, Allow authToken to be a function, and Fix wrong placeholder numbering when a `from` source is a `{fragment, schema}` tuple.
♥

$ log Elixir & Phoenix --recent

Elixir trims Calendar.ISO parsing and weekday math, densifies coverage accounting 6 shipped File stat functions accept open handles, Keyword.drop aligns its membership check 5 shipped phx.new templates pin a Tailwind CLI that fails on macOS, LiveView starts 1.3.0-dev 3 shipped Elixir reverts duplicate alias detection, stale test deps resolve from source records 8 shipped

$ log --all # elsewhere on the wire

@openclaw Cold-start Gateway diagnostics stop crying wolf, doctor repairs plugin drift Agentic Coding Cline desktop bundles shrink, goose unblocks its own clicks

$ ls showcases/

Rails Django Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.