v7.0.0

heroku/ruby

Changed

• Default Ruby version is now 3.3.7 and default bundler version is now 2.5.23 (#408)

Fixed

• The docker run command no longer requires an entrypoint when using default processes provided by heroku/ruby directly (and not the heroku/procfile buildpack) (#404)

v6.0.0

heroku/ruby

Changed

• Gem install behavior and configuration (#402)
  • Gem install path is now configured with GEM_HOME and GEM_PATH instead of BUNDLE_PATH.
  • Cleaning gems is now accomplished via running bundle clean --force. Previously it was accomplished by setting BUNDLE_CLEAN=1.
  • The BUNDLE_DEPLOYMENT=1 environment variable is changed to BUNDLE_FROZEN=1.
  • The BUNDLE_BIN environment variable is no longer set.

v5.1.0

heroku/ruby

Changed

• Enabled libcnb's trace feature. (#398)

v5.0.1

heroku/ruby

Fixed

• Executables from the applications bin directory will be placed on the path before dependencies installed via bundler (#383)
• Binaries from user installed gems will be placed on the path before binaries that ship with Ruby (#383)

v5.0.0

heroku/ruby

Changed

• Default Ruby version is now 3.2.6 (#374)
• Default Bundler version is now 2.5.6 (#374)

v4.0.2

heroku/ruby

Fixed

• Ruby pre-release verssions like 3.4.0.rc1 now work as expected. (#372)
• Layer metadata deserialization to Rust structs is now using #[serde(deny_unknown_fields)] this prevents the accidental scenario where metadata containing a superset of fields could accidentally be deserialized to the wrong struct. It's unlikely this is currently happening with the current buildpack, but it's a possibly-observable difference so it's being listed (#371)

v4.0.1

heroku/ruby

Fixed

• A bug introduced in 4.0.0 would result in incorrectly skipping running bundle install when the Gemfile or Gemfile.lock or environment variables had changed. The bug is now fixed. (#364)

v4.0.0

heroku/ruby

Changed

• Default process types defined by the Ruby buildpack now use IPv6 host :: which is equivalent of IPv4 host 0.0.0.0. This will only affect applications that do not define a web process type via the Procfile and Procfile Cloud Native Buildpack. Those applications must make sure to update their configuration to bind to an IPv6 host. (#354)

Added

• The buildpack now warns the user when environmental variables used in running the default process are not defined. (#307)

v3.0.0

heroku/ruby

Changed

• The buildpack now implements Buildpack API 0.10 instead of 0.9, and so requires lifecycle 0.17.x or newer. (#283)

Added

• Added support for Ubuntu 24.04 (and thus Heroku-24 / heroku/builder:24). (#284)

v2.1.3

heroku/ruby

Changed

• The fun_run commons library was moved to it's own crate (#232)

Added

• Raise a helpful error when a file cannot be accessed at the time of buildpack detection (#243)