Repository navigation
Rails 8.1 current, dual-boot with Rails main - #49
Merged
Merged
Conversation
- Gemfile: 8.1 current, rails/rails main next (8.2.0.alpha) - rspec-rails from GitHub main on the next side (7.1.1 raises a FrozenError in view specs on Rails main) - Collapse the 8.1 NextRails.next? branches (next side wins) - CI: the Gemfile.next job no longer blocks the build Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
etagwerker
marked this pull request as ready for review
November 22, 2026 02:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Makes Rails 8.1.4.1 the current version and dual-boots against Rails
main(8.2.0.alpha at6ef561e) as the next version. It's one commit on top of #48, so this PR is stacked onupgrade-rails-8.1-dual-bootand its base is that branch. Merge #48 first, then retarget this one tomain.Gemfileruns 8.1 andGemfile.nextruns Railsmain. The suite is green on both (83 examples, 0 failures).What changed
if next?now picksgithub: "rails/rails", branch: "main", and the else side picks~> 8.1.0.max_connectionsindatabase.yml, and theto_time_preserves_timezoneoverride is gone. NoNextRails.next?calls are left inapp,config,liborspec.mainon the next side only. 7.1.1 raises aFrozenErrorin the three view specs on Railsmain(view.lookup_context.prefixesis frozen). The current side stays on the released rspec-rails 7.1.1.Gemfile.nextjob is nowcontinue-on-error. Railsmainmoves daily, so a red job there is a heads up, not a blocker. TheGemfilejob still blocks.Gemfile.lockis the 8.1.4.1 lockfile.Gemfile.next.lockpins Railsmainto6ef561eand rspec-railsmain, so refresh it withBUNDLE_GEMFILE=Gemfile.next bundle update rails rspec-railswhen you want to look at newer edge.Things worth a close look
main:config.active_record.raise_on_assign_to_attr_readonlyis deprecated and goes away in Rails 9.0. It comes fromload_defaults 7.0(the app doesn't set it), so I left it for theload_defaultsfollow-up PRs.ombu_labs-auth1.2, see Upgrade Rails to 8.0, dual-boot with 8.1 #48).load_defaultsis still 7.0.mainis pre-release. Nothing here should ship to production on that side.Verification
bundle exec rspeconGemfile(8.1.4.1): 83 examples, 0 failures, noDEPRECATION WARNINGlinesbundle exec rspeconGemfile.next(8.2.0.alpha): 83 examples, 0 failures, 1 deprecation (above)🤖 Generated with Claude Code