Upgrade Ruby to 4.0 and enable depreciation warnings in local, CI, and Elastic Beanstalk - #516
Open
cycomachead wants to merge 2 commits into
Open
Upgrade Ruby to 4.0 and enable depreciation warnings in local, CI, and Elastic Beanstalk#516cycomachead wants to merge 2 commits into
cycomachead wants to merge 2 commits into
Conversation
- Update Ruby version to 4.0.6 across local, CI, Docker, and EB environments - Bump Bundler to 4.0.16 to match Ruby 4.0 defaults - Enable Ruby-level deprecation warnings globally in `config/boot.rb` - Enable Rails deprecation logging in production to surface upgrade issues - Update RuboCop and documentation to reflect the new target version Co-authored-by: Claude Code <noreply@anthropic.com>
20 tasks
Resolves the Ruby-version conflicts between this branch's 4.0.6 upgrade and main's revert to a 3.3-compatible deploy story: - Gemfile: ruby '>= 3.4', '< 5' so EB can deploy on a Ruby 3.4 or 4.0 platform branch while local dev, CI, and Docker stay on 4.0.6. - buildspec.yml: build with Ruby 3.4 to match the EB platform; must be bumped together with any EB platform change. - RuboCop targets 3.4 (the minimum Ruby the app must run on). - Gemfile.lock rebuilt from main's (keeps good_job etc.), Bundler 4.0.18. Verified: frozen bundle install succeeds on 3.4.10, is rejected on 3.3, and RSpec (660 examples) + Cucumber rack_test (24 scenarios) + RuboCop all pass on 4.0.6. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
General Info
Changes
Upgrades Ruby from 3.4.10 to 4.0.6 across all environments (local, CI, Docker, Elastic Beanstalk) and enables deprecation warnings globally so upgrade-related issues surface everywhere, including production.
Ruby version bump:
.tool-versions,Gemfile,Dockerfile,.devcontainer/Dockerfile→ Ruby 4.0.6Gemfile.lockregenerated withRUBY VERSION ruby 4.0.6p0.rubocop.yml→TargetRubyVersion: 4.0docs/developers.mdsetup instructions updatedCI:
ruby-version: .tool-versionsand pick up the bump automaticallydocs.ymlhad a hardcoded'3.4'→ updated to'4.0'Elastic Beanstalk:
buildspec.yml→ruby: 4.0.platform/hooks/prebuild/01_install_bundler.sh→ installs Bundler 4.0.16 to match the lockfileDeprecation warnings:
Warning[:deprecated] = truemoved from dev/test env files intoconfig/boot.rbso it applies in every environment, including productionreport_deprecations = falsetoreport_deprecations = true+deprecation = :logso Rails deprecations are visible in production logsTesting
bundle installand app boot verified on Ruby 4.0.6Documentation
Developer setup instructions in
docs/developers.mdupdated to reference Ruby 4.0.Checklist
Superconductor Ticket Implementation | App Preview | Guided Review