Description:
During dependency installation, we received a notice that the i18n gem will drop support for Ruby versions lower than 3.2 in April 2025 (see Ruby EOL schedule).
Post-install message from i18n: PSA: I18n will be dropping support for Ruby < 3.2 in the next major release (April 2025), due to Ruby's end of life for 3.1 and below (https://endoflife.date/ruby). Please upgrade to Ruby 3.2 or newer by April 2025 to continue using future versions of this gem.
To ensure long-term compatibility, security, and maintainability, we should plan to upgrade the application’s Ruby version to 3.3.x.
Benefits of upgrading:
-
Future compatibility with critical gems (i18n, rails, etc.)
-
Security patches and performance improvements from Ruby 3.3
-
Staying ahead of the April 2025 EOL deadline
Proposed steps:
-
Update the Ruby version in .ruby-version or Dockerfile/CI configuration.
-
Update any related dependencies that require specific Ruby versions.
-
Run the test suite and resolve any issues. (wait... do we even have a test suite?)
-
Deploy the updated Ruby version to staging and do smoke testing.
-
Deploy to production after verification.
Note: Verify that all production servers and CI/CD pipelines support Ruby 3.3.x. I'm not sure if there would be any potential issues here with our deploy pipelines, but we'd want to make sure that wouldn't be an issue before updating
Description:
During dependency installation, we received a notice that the i18n gem will drop support for Ruby versions lower than 3.2 in April 2025 (see Ruby EOL schedule).
Post-install message from i18n: PSA: I18n will be dropping support for Ruby < 3.2 in the next major release (April 2025), due to Ruby's end of life for 3.1 and below (https://endoflife.date/ruby). Please upgrade to Ruby 3.2 or newer by April 2025 to continue using future versions of this gem.To ensure long-term compatibility, security, and maintainability, we should plan to upgrade the application’s Ruby version to 3.3.x.
Benefits of upgrading:
Future compatibility with critical gems (i18n, rails, etc.)
Security patches and performance improvements from Ruby 3.3
Staying ahead of the April 2025 EOL deadline
Proposed steps:
Update the Ruby version in .ruby-version or Dockerfile/CI configuration.
Update any related dependencies that require specific Ruby versions.
Run the test suite and resolve any issues. (wait... do we even have a test suite?)
Deploy the updated Ruby version to staging and do smoke testing.
Deploy to production after verification.
Note: Verify that all production servers and CI/CD pipelines support Ruby 3.3.x. I'm not sure if there would be any potential issues here with our deploy pipelines, but we'd want to make sure that wouldn't be an issue before updating