Draft
Conversation
Member
JuanVqz
commented
Apr 16, 2026
JuanVqz
commented
- Make it work with ruby 3.2
- Upgrade Rails 7.0.10 to 7.1.6
- Gemfile: bump to rails ~> 7.1.6, keep next_rails for future hops
- config/application.rb: load_defaults 7.1, add_autoload_paths_to_load_path = false
- config/environments/{dev,test,prod}.rb: cache_classes -> enable_reloading
- spec/rails_helper.rb: fixture_path -> fixture_paths (plural, 7.1 API)
Process: dual-booted with next_rails, ran breaking-change detection against
rails-upgrade skill's 7.1 patterns, fixed each with NextRails.next? branches
under Gemfile.next, then consolidated once 7.1 went green. load_defaults 7.1
flags flipped via the rails-load-defaults skill.
Not flipped: action_view.sanitizer_vendor, action_text.sanitizer_vendor.
Rails::HTML constant isn't loaded at initializer time because config/application.rb
uses selective railtie loading (no action_text, no active_storage). App doesn't
use sanitize/strip_tags/Action Text, so harmless. load_defaults 7.1 applies the
internal defaults via a different code path that doesn't fail.
Tailwind: move app/assets/stylesheets/application.tailwind.css to
app/assets/tailwind/application.css and rewrite for Tailwind v4
(@import "tailwindcss", @reference in component layer). Disclaimer: this
was already broken before the Rails upgrade — tailwindcss-rails 4.4.0 (which
ships Tailwind v4) was already in Gemfile.lock on the base branch, but the
CSS file was still using v3 syntax and the v3 default path. The Rails upgrade
did not cause this; it only surfaced during the smoke test.
Tests: 5/5 passing on Rails 7.1.6. Only residual deprecation is
Rails.application.secrets coming from a dependency's internals — flagged for
the 7.1 -> 7.2 hop.
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
1 participant
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.