Skip to content

Releases: heroku/buildpacks-ruby

v4.0.0

27 Nov 16:28
ee5ee01
Compare
Choose a tag to compare

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

17 May 19:46
1926adf
Compare
Choose a tag to compare

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

18 Mar 21:52
3e9677f
Compare
Choose a tag to compare

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)

v2.1.2

31 Oct 14:24
4f514f6
Compare
Choose a tag to compare

heroku/ruby

Fixed

  • Update build logging style (#198)

v2.1.1

24 Oct 13:26
54845ff
Compare
Choose a tag to compare

heroku/ruby

Fixed

  • Updated buildpack display name, description and keywords. (#223)

v2.1.0

26 Sep 20:27
e59d82c
Compare
Choose a tag to compare

heroku/ruby

Added

  • Introduce heroku build metrics support (#172)
  • Changelog moved to be per-crate rather than for the whole project (#154)

v2.0.1

25 Jul 20:06
2901419
Compare
Choose a tag to compare

heroku/ruby

  • Commons: Introduce build_output module (#155)
  • Commons: Remove gem_list, rake_status, rake_task_detect modules (#155)
  • Commons: EnvCommand removed, replaced with fun_run (#139)

v2.0.0

02 Aug 12:20
7104c62
Compare
Choose a tag to compare

heroku/ruby

  • Initial version of Ruby buildpack in Rust (#93)
  • Version 2.0.0 for the first release is not a typo. There was an issue in pack where a builder with the same name and version number would reuse artifacts left on image from prior runs which caused issues. There were prior releases of heroku/ruby CNB from different sources that triggered this problem. To ensure no one would encounter that issue we developed and released using a version we know has not been used before. Version 2.0 was the first major version without a prior release of heroku/ruby CNB from any source.