Who contributed to Rails on August 1, 2026?

6 developers shipped this update, including jeremy, dependabot, viralpraxis, Xavier Noria, Ryuta Kamizono, and Mike Dalessio.

What were the notable Rails updates?

Structured provider errors, push instrumentation, and Retry-After-aware retries, Merge pull request #58332 from rails/fxn/revert, and Deprecate positional `pk`, `id_value`, and `sequence_name` for `#insert`.

@rails

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

github ↗

Pick a date

Topics: Ruby Full archive →

The Wire · Showcase

RAILS HARDENS ERROR HANDLING FOR PUSH NOTIFICATIONS, REVERTS SCHEMA DUMP BREAKING CHANGE

By RepoJournal · Filed 06:55 UTC on August 1, 2026 · About Rails

6 people shipped this

dependabot @dependabot 3 cited

jeremy @jeremy 1 cited

viralpraxis @viralpraxis 1 cited

Xavier Noria @fxn 1 cited

Ryuta Kamizono @kamipo 1 cited

Mike Dalessio @flavorjones

Action Push Native shipped structured provider errors with retry semantics while Rails core pulled back a migrations filter removal that broke existing workflows.

The action_push_native gem now surfaces what push providers already tell us: all errors inherit from a new `ActionPushNative::Error` base carrying `service`, `status`, `reason`, and `retry_after` [1]. This means APNs failures now expose numeric HTTP status codes and parsed reason tokens like `TooManyRequests` and `BadDeviceToken`, letting you build intelligent retry logic instead of scraping error messages. Existing error rescuers stay intact because the message remains the first positional argument.

Meanwhile, Rails core reverted a recent commit that removed the migrations filter from schema dumps [2], a change that broke existing workflows for teams relying on the filtered behavior. Xavier Noria merged the revert alongside a deprecation for positional arguments in the `insert` method [3], clarifying that `pk`, `id_value`, and `sequence_name` should now use keyword arguments with `returning:` for cleaner semantics. The core team also fixed test flakiness by making sure ActiveRecord tests don't rely on implicit MVCC-based ordering [4], catching issues with the new `pg_disorder` extension in reverse mode.

Dependabot kept the ecosystem moving with updates to googleauth 1.17.3 [5], httpx 1.7.6 [6], and rubocop 1.86.1 [7] across the push native and sanitizer repos. This period saw 15 commits and 12 PRs across 4 repos.

Action items

→ Upgrade action_push_native to capture structured provider errors and add retry-after awareness to your push handlers rails/action_push_native [plan]
→ Review your schema dump generation if you depend on migrations filtering behavior - the recent removal was reverted rails/rails [monitor]
→ Start migrating `insert` calls from positional `pk`, `id_value`, `sequence_name` to keyword `returning:` argument rails/rails [plan]

References

[1] Structured provider errors, push instrumentation, and Retry-After-aware retries ↗ rails/action_push_native
[2] Merge pull request #58332 from rails/fxn/revert rails/rails
[3] Deprecate positional `pk`, `id_value`, and `sequence_name` for `#insert` rails/rails
[4] `activerecord`: make sure tests do not rely on implicit `SELECT` order ↗ rails/rails
[5] Bump googleauth from 1.16.1 to 1.17.3 ↗ rails/action_push_native
[6] Bump httpx from 1.6.3 to 1.7.6 ↗ rails/action_push_native
[7] Bump rubocop from 1.82.1 to 1.86.1 ↗ rails/action_push_native

Quick answers

What shipped in Rails on August 1, 2026?: Action Push Native shipped structured provider errors with retry semantics while Rails core pulled back a migrations filter removal that broke existing workflows. In total, 15 commits and 12 pull requests landed.
Who contributed to Rails on August 1, 2026?: 6 developers shipped this update, including jeremy, dependabot, viralpraxis, Xavier Noria, Ryuta Kamizono, and Mike Dalessio.
What were the notable Rails updates?: Structured provider errors, push instrumentation, and Retry-After-aware retries, Merge pull request #58332 from rails/fxn/revert, and Deprecate positional `pk`, `id_value`, and `sequence_name` for `#insert`.

RAILS FIXES PLUCK REGRESSION, BOOTSNAP DITCHES MARSHAL FOR MSGPACK

Rails patched a critical regression in association plucking for new records that broke `ids` queries overnight, while bootsnap replaced Date marshalling with faster, more compact msgpack serialization.

ruby 40 shipped

@rails Aug 5

RAILS HARDENS FILE STORAGE, UNIFIES FOREIGN KEY HANDLING ACROSS 22 COMMITS

Rails killed a filesystem vulnerability while Propshaft eliminates globbing from production asset lookups in coordinated pushes toward Ractor compatibility.

ruby 35 shipped

@rails Aug 4

Rails fixes composite foreign key tracking across counter cache and autosave

Belongs_to associations with aliased or composite foreign keys were silently failing change detection, breaking counter cache increments, touch callbacks, and validation.

ruby 25 shipped

@rails Aug 3

RAILS RESTORES ALIAS_ATTRIBUTE IN ASSOCIATIONS, FIXES SILENT FAILURES

A performance optimization from Rails 4.2 has been quietly breaking alias_attribute in associations for years, and it's finally fixed.

ruby 23 shipped

Elsewhere on the wire

AI Agents Aug 6

LANGCHAIN HARDENS ANTHROPIC TOOL CALLING AND GIT CREDENTIALS AS OPENHANDS SHIPS 1.10.0

LangChain fixed a critical credential leak in evaluation runs while Anthropic tool schemas get proper fallback handling, as three major agent frameworks push releases across the ecosystem.

ai-agents 54 shipped

Local LLMs Aug 6

OLLAMA FIXES KV CACHE CORRUPTION, LLAMA.CPP HARDENS FILE SEARCH, VLLM KILLS MOE LEGACY CODE

Ollama patched a critical cache corruption bug that corrupts lazy snapshots during multi-request prefills, while llama.cpp hardened Windows junction traversal and vLLM removed 14 hardcoded MoE shards across quantization methods.