issue-link js-issue-link" data-error-text="Failed to load title" data-id="3633254694" data-permission-text="Title is private" data-url="https://github.com/hotwired/turbo-rails/issues/761" data-hovercard-type="pull_request" data-hovercard-url="/hotwired/turbo-rails/pull/761/hovercard" href="https://github.com/hotwired/turbo-rails/pull/761">#761][] and [883a19e][] The changes introduced in #761 were passing for all Ruby and Rails version combinations with the exception of `ruby@3.1` and `rails@7.1`. Following that commit's merging, the change in [883a19e][] removed support for `ruby@3.1` and replaced it with `ruby@3.2`. However, that version still fails in the same way that its preceding commit fails. This commit guards the assertion so that it is skipped for any `ruby@3.2` entry in the CI matrix. Rather than resolve the issue, this commit aims to restore a green suite for other commits to be merged into. We can resolve the underlying issue in the future, or wait until [March of 2026 when Ruby 3.2 becomes EOL][eol]. [#761]: #761 [883a19e]: 883a19e [eol]: https://www.ruby-lang.org/en/downloads/branches/

Fix CI for `ruby@3.2.x`-`rails@7.2.x`#764seanpdoyle merged 1 commit intomainhotwired/turbo-rails:mainfrom pass-cihotwired/turbo-rails:pass-ciCopy head branch name to clipboard

Commits

Commits on Nov 21, 2025

Fix CI for `ruby@3.2.x`-`rails@7.2.x`

Fix CI for `ruby@3.2.x`-`rails@7.2.x`#764
seanpdoyle merged 1 commit intomainfrom
pass-ci