Who contributed to Rails on July 24, 2026?

6 developers shipped this update, including Hartley McGuire, Jean Boussier, Amanda Perino, rosa, Tom Blais, and mhenrixon.

What were the notable Rails updates?

v1.5.0, Prevent concurrency lock leaks that cause duplicate job execution, and Prevent wrong release of blocked jobs and semaphore corruption.

@rails

Ruby on Rails - Shopify, Basecamp, GitHub all run on it

github ↗

Pick a date

Topics: Ruby Full archive →

The Wire · Showcase

SOLID QUEUE 1.5.0 SHIPS WITH CRITICAL CONCURRENCY FIXES

By RepoJournal · Filed 06:55 UTC on July 24, 2026 · About Rails

6 people shipped this

Jean Boussier @byroot 2 cited

rosa @rosa 2 cited

Hartley McGuire @skipkayhil 1 cited

Tom Blais @tblais1224 1 cited

mhenrixon @mhenrixon 1 cited

Amanda Perino @AmandaPerino

Solid Queue v1.5.0 lands three separate fixes for a production bug that corrupts semaphore counts and lets concurrency-limited jobs run wild.

The release [1] closes a dangerous class of failure where workers with `limits_concurrency` could permanently leak their semaphore permits, allowing jobs to execute far beyond their configured limits. Two independent production reports converged on the same root cause [2], and the fix was ported from starburstlabs/solid_queue after being diagnosed in the wild [3]. The bug manifests when a worker's database heartbeat fails transiently: a supervisor prunes it as dead, releases its concurrency lock, and unblocks replacements, but the semaphore value never gets properly capped. Three separate PRs address it [2], [3], [4]: guarding `signal_all` against incrementing beyond limit, preventing wrong release of blocked jobs, and capping semaphore increments per concurrency group. Beyond the critical fix, v1.5.0 drops Ruby 3.1 support [1], improves PostgreSQL polling for unspecified queue names, introduces `bin/job check` for configuration validation, and adds default time zone support for recurring tasks. Rails core continues cleanup work across the stack: removing dead branches in MySQL introspection [5], , stripping unused code from Railties and Action Cable [6], and excising dead test runner helpers [7].

Action items

→ Upgrade solid_queue to 1.5.0 before next deploy if you use limits_concurrency rails/solid_queue [immediate]
→ Review any recurring jobs to set default time zone if needed rails/solid_queue [plan]
→ Update Ruby requirement if pinned to 3.1 rails/solid_queue [plan]

References

[1] v1.5.0 ↗ rails/solid_queue
[2] Prevent concurrency lock leaks that cause duplicate job execution ↗ rails/solid_queue
[3] Prevent wrong release of blocked jobs and semaphore corruption rails/solid_queue
[4] Guard signal_all against incrementing semaphore beyond its limit rails/solid_queue
[5] Remove dead branch in MySQL column introspection rails/rails
[6] Merge pull request #58223 from 55728/remove-unused-railties-actioncable rails/rails
[7] Merge pull request #58216 from Shopify/rubydex/remove-test-runner-path-parser rails/rails

Quick answers

What shipped in Rails on July 24, 2026?: Solid Queue v1.5.0 lands three separate fixes for a production bug that corrupts semaphore counts and lets concurrency-limited jobs run wild. In total, 27 commits, 17 pull requests, and 1 releases landed.
Who contributed to Rails on July 24, 2026?: 6 developers shipped this update, including Hartley McGuire, Jean Boussier, Amanda Perino, rosa, Tom Blais, and mhenrixon.
What were the notable Rails updates?: v1.5.0, Prevent concurrency lock leaks that cause duplicate job execution, and Prevent wrong release of blocked jobs and semaphore corruption.

Rails Strips Dead Code, Solid Queue Hardens Tests and Drops Ruby 3.1

Aaron Patterson is cleaning up Rails internals while Solid Queue fixes flaky CI and raises its minimum Ruby version to 3.2.

ruby 17 shipped 1-min read

@rails 2 days ago

RAILS CORE CLEANS HOUSE WITH FOUR DEPRECATION SWEEPS

Rails is systematically removing unused internals across Journey, RedisCacheStore, and test utilities, signaling a major cleanup push before the next major version.

ruby 74 shipped 1-min read

@rails 3 days ago

SOLID QUEUE CUTS JOB DISPATCH OVERHEAD, RAILS FIXES SCHEMA MIGRATION DEFAULTS

Solid Queue eliminated redundant database queries in its hottest path, cutting unnecessary round-trips on every bulk job enqueue while Rails corrected a schema.rb default it shipped with reservations.

ruby 20 shipped 2-min read

@rails 4 days ago

SOLID_QUEUE CLEANS UP CONFIG ERROR HANDLING

Solid Queue unified its fractured error and warning system, ending the inconsistency that made configuration failures hard to debug.

ruby 4 shipped 1-min read

Elsewhere on the wire

AI Agents about 1 hour ago

LANGCHAIN SHIPS COORDINATED PROVIDER UPDATES WITH LANGSMITH GATEWAY SUPPORT

All four core LangChain packages bumped to 1.5.1 overnight with unified LangSmith gateway routing and provider-specific fixes across OpenAI, Anthropic, and Fireworks.

ai-agents 62 shipped 1-min read

Local LLMs about 1 hour ago

LLAMA.CPP SHIPS FIVE RELEASES IN 24 HOURS, FIXES SPECULATIVE DECODING ACROSS THE STACK

The inference stack is consolidating around speculative decoding, and the bugs surfacing there are getting squashed across three major projects simultaneously.

llms 157 shipped 2-min read

@CachyOS about 1 hour ago

INSTALLER REFACTOR TAKES SHAPE, PACKAGE UPDATES ROLL STEADY

CachyOS is modernizing its CLI installer with a comprehensive typed partition system overhaul while maintaining smooth automation across the AUR-derived package repository.

infra 57 shipped 1-min read

Elixir & Phoenix about 1 hour ago

PHOENIX LIVE VIEW SEALS CRITICAL NODE NAME LEAK IN UPLOAD TOKENS

A reverted encryption fix exposes how Phoenix was leaking BEAM node identities through unencrypted upload tokens, and the core team is pivoting to a cleaner solution using term_to_binary.