Why
Two small gem bumps grouped because each is a couple of lines.
Globalize 6.3.0 declares activemodel/activerecord >= 4.2, < 7.2 — a hard resolution blocker for Rails 7.2, same as Mongoid. Globalize 7.1.3 declares >= 7.0, < 8.2, so it supports Rails 7.1 through 8.1 and can land before the framework bump.
Puma 5.6.8 is end of life. Not required by Rails, but it is pinned to an exact version in the Gemfile and needs to move eventually; doing it here keeps it off the Rails PR.
Scope
globalize 6.3.0 -> ~> 7.1 — small surface (translated ActiveRecord attributes)puma 5.6.8 -> ~> 6.6 — check config/puma.rb against Puma 6 semantics. It uses before_fork with ActiveRecord::Base.connection_pool.disconnect! and on_worker_boot with ActiveRecord::Base.establish_connection, both of which Rails now largely handles itself.
Verified both resolve cleanly against Rails 7.1.
Acceptance criteria
Blocked by
#880 (upgrade prep). Independent of #881 — can run in parallel. Blocks #883.
Part of the Ruby + Rails upgrade sequence. Ruby 3.2 reached end of life on 2026-04-01 and the backend is on Rails 7.1; the goal is Ruby 3.4.10 and Rails 8.1, in steps that each keep CI green and are independently deployable.
Why
Two small gem bumps grouped because each is a couple of lines.
Globalize 6.3.0 declares
activemodel/activerecord >= 4.2, < 7.2— a hard resolution blocker for Rails 7.2, same as Mongoid. Globalize 7.1.3 declares>= 7.0, < 8.2, so it supports Rails 7.1 through 8.1 and can land before the framework bump.Puma 5.6.8 is end of life. Not required by Rails, but it is pinned to an exact version in the Gemfile and needs to move eventually; doing it here keeps it off the Rails PR.
Scope
globalize6.3.0 ->~> 7.1— small surface (translated ActiveRecord attributes)puma5.6.8 ->~> 6.6— checkconfig/puma.rbagainst Puma 6 semantics. It usesbefore_forkwithActiveRecord::Base.connection_pool.disconnect!andon_worker_bootwithActiveRecord::Base.establish_connection, both of which Rails now largely handles itself.Verified both resolve cleanly against Rails 7.1.
Acceptance criteria
Blocked by
#880 (upgrade prep). Independent of #881 — can run in parallel. Blocks #883.
Part of the Ruby + Rails upgrade sequence. Ruby 3.2 reached end of life on 2026-04-01 and the backend is on Rails 7.1; the goal is Ruby 3.4.10 and Rails 8.1, in steps that each keep CI green and are independently deployable.