Skip to content

Test every supported Rails and Ruby; require Rails 7.1+ / Ruby 3.2+ - #100

Merged
fractaledmind merged 1 commit into
mainfrom
chore/ci-matrix
Oct 13, 2026
Merged

fractaledmind merged 1 commit into
mainfrom
chore/ci-matrix

Conversation

@fractaledmind

Copy link
Copy Markdown
Owner

CI tested one locked Rails (7.2.0) across Ruby 3.1–3.4, so main looked green while:

  • the locked Rails can't boot on Ruby 4.0 (benchmark left the default gems),
  • Rails 7.1 and 8.0 fail against json 3.1 (unknown keyword: quirks_mode from their JSON encoder),
  • the dummy app no longer boots on Rails 7.0 (autoload_lib).

This PR runs tests on Ruby 3.2 / 3.3 / 3.4 / 4.0 × Rails 7.1 / 7.2 / 8.0 / 8.1 through gemfiles/, and runs Standard once in its own job. The gemspec now requires Rails ≥ 7.1 and Ruby ≥ 3.2, dropping only Rails 7.0, which is EOL and was already untestable.

The 7.1 and 8.0 gemfiles pin json < 3. Apps on those Rails lines with json 3.1 hit the same encoder error, but that comes from Rails, not from this gem.

Also included: Gemfile.lock refreshed to Rails 8.1, the one new Standard offense fixed (lines.join — BacktraceLine defines only to_s), and actions/checkout v6, which supersedes #91.

🤖 Generated with Claude Code

… / Ruby 3.2

CI ran one locked Rails (7.2.0) across Ruby 3.1-3.4, so it never saw that
the locked Rails cannot boot on Ruby 4.0, that Rails 7.1 and 8.0 break
against json 3.1, or that the dummy app no longer boots on Rails 7.0.

- Matrix Ruby 3.2/3.3/3.4/4.0 x Rails 7.1/7.2/8.0/8.1 via gemfiles/
- Lint once in its own job instead of in every matrix cell
- Drop Rails 7.0 (EOL) and Ruby < 3.2 from the gemspec
- Refresh Gemfile.lock to Rails 8.1 so `bundle exec rake` runs on Ruby 4.0
- Fix the Style/MapJoin offense newer Standard reports
- actions/checkout v6

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@fractaledmind
fractaledmind merged commit cad7b33 into main Oct 13, 2026
17 checks passed
@fractaledmind
fractaledmind deleted the chore/ci-matrix branch October 13, 2026 12:10
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