Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare release v4.0.0 #356

Merged
merged 1 commit into from
Nov 27, 2024
+5 −2
Merged

Prepare release v4.0.0 #356

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion buildpacks/ruby/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [4.0.0] - 2024-11-27

### 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](https://github.com/heroku/buildpacks-procfile). Those applications must make sure to update their configuration to bind to an IPv6 host. ([#354](https://github.com/heroku/buildpacks-ruby/pull/354))
Expand Down Expand Up @@ -65,7 +67,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Initial version of Ruby buildpack in Rust (https://github.com/heroku/buildpacks-ruby/pull/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](https://github.com/buildpacks/pack/issues/1322#issuecomment-1038241038). 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.

[unreleased]: https://github.com/heroku/buildpacks-ruby/compare/v3.0.0...HEAD
[unreleased]: https://github.com/heroku/buildpacks-ruby/compare/v4.0.0...HEAD
[4.0.0]: https://github.com/heroku/buildpacks-ruby/compare/v3.0.0...v4.0.0
[3.0.0]: https://github.com/heroku/buildpacks-ruby/compare/v2.1.3...v3.0.0
[2.1.3]: https://github.com/heroku/buildpacks-ruby/compare/v2.1.2...v2.1.3
[2.1.2]: https://github.com/heroku/buildpacks-ruby/compare/v2.1.1...v2.1.2
Expand Down
2 changes: 1 addition & 1 deletion buildpacks/ruby/buildpack.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ api = "0.10"

[buildpack]
id = "heroku/ruby"
version = "3.0.0"
version = "4.0.0"
name = "Heroku Ruby"
homepage = "https://github.com/heroku/buildpacks-ruby"
description = "Heroku's buildpack for Ruby applications."
Expand Down