Skip to content

Add non-blocking Rails main entry to CI matrix - #1034

Merged
jnunemaker merged 1 commit into
mainfrom
ci-rails-main
Jul 25, 2026
Merged

Add non-blocking Rails main entry to CI matrix#1034
jnunemaker merged 1 commit into
mainfrom
ci-rails-main

Conversation

@jnunemaker

Copy link
Copy Markdown
Collaborator

Why

Rails main went keyword-only for Arel::Table.new (rails/rails#57021), which broke get_all in the ActiveRecord adapter. The fix landed in #1003, but CI had no way to catch the regression because the matrix only covers released Rails versions.

What

  • Adds a ruby 3.3 / rails main entry to the CI matrix via include, installing Rails from rails/rails@main (currently resolves to 8.2.0.alpha)
  • continue-on-error: ${{ matrix.rails == 'main' }} makes it a non-blocking canary — edge Rails breakage annotates the run but doesn't fail the build
  • Gemfile installs Rails from git when RAILS_VERSION=main, otherwise behaves exactly as before
  • SQLITE3_VERSION uses 2.1.0 for main (same as 8.0.0)

Verified locally that RAILS_VERSION=main bundle lock resolves cleanly.

🤖 Generated with Claude Code

Rails main went keyword-only for Arel::Table.new (rails/rails#57021),
which broke get_all in the ActiveRecord adapter (#1003) — and nothing
in CI could catch it because the matrix only covers released versions.

Run ruby 3.3 against rails/rails main as a canary. continue-on-error
keeps it from blocking the build when edge Rails breaks.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@jnunemaker
jnunemaker merged commit 13b05d2 into main Jul 25, 2026
46 of 47 checks passed
@jnunemaker
jnunemaker deleted the ci-rails-main branch July 25, 2026 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant