Skip to content

Conversation

@ramonskie
Copy link
Contributor

Summary

Ruby 3.1 reached end-of-life on March 26, 2025 and is no longer receiving security updates per the official Ruby maintenance schedule.

This PR removes Ruby 3.1.x from the buildpack.

Changes

  • ✅ Removed Ruby 3.1.6 and 3.1.7 dependency entries from manifest.yml (both cflinuxfs3 and cflinuxfs4 stacks)
  • ✅ Removed Ruby 3.1.x deprecation notice from manifest.yml
  • ✅ Removed Ruby 3.1.3 reference from java-index/index.yml
  • ✅ Updated test fixtures to use Ruby 3.2.x instead of 3.1.x:
    • fixtures/multibuildpack/rails6/Gemfile
    • fixtures/default/rails7/Gemfile
    • fixtures/default/rails6_sprockets/Gemfile
    • fixtures/default/custom_gemfile/Gemfile-APP

Notes

  • JRuby 9.4.8.0 (which has Ruby 3.1 compatibility) was intentionally left in the manifest as it's a separate runtime and not affected by MRI Ruby 3.1 EOL
  • The CHANGELOG entries referencing 3.1 were left as historical records

References

Ruby 3.1 reached end-of-life on March 26, 2025 and is no longer
receiving security updates.

Changes:
- Remove Ruby 3.1.6 and 3.1.7 from manifest.yml dependencies
- Remove Ruby 3.1.x deprecation notice from manifest.yml
- Remove Ruby 3.1.3 from java-index
- Update test fixtures to use Ruby 3.2.x instead of 3.1.x

Refs: https://www.ruby-lang.org/en/downloads/branches/
Copy link
Contributor

@ivanovac ivanovac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

- Upgrade Rails 6.1 -> Rails 7.2 in test fixtures
  - Rename rails6_sprockets -> rails72_sprockets
  - Rename multibuildpack/rails6 -> multibuildpack/rails72
  - Rails 6.1 is EOL (June 2024) and has Ruby 3.2 compatibility issues

- Add rackup gem to all Rack-based applications
  - Required since rackup was extracted from Ruby stdlib in Ruby 3.0+
  - Added to Sinatra, custom Gemfile, and multibuildpack fixtures
  - Updated vendor/cache for fixtures that use cached gems

- Update JRuby fixture for Ruby 3.2 compatibility
  - Upgrade gem dependencies (Sinatra 3.0 -> 4.2, Rack 2.2 -> 3.2)
  - Add universal-java-1.8 platform to Gemfile.lock
  - Regenerate lockfile and vendor/cache with JRuby 9.4.8.0

- Regenerate all Gemfile.lock files with Ruby 3.2.9

All integration tests passing (15/15)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants