Update lifecycle from v0.14.1 to v0.15.3 #307
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Release notes: https://github.com/buildpacks/lifecycle/releases/tag/v0.14.2 https://github.com/buildpacks/lifecycle/releases/tag/v0.14.3 https://github.com/buildpacks/lifecycle/releases/tag/v0.15.0 https://github.com/buildpacks/lifecycle/releases/tag/v0.15.1 https://github.com/buildpacks/lifecycle/releases/tag/v0.15.2 https://github.com/buildpacks/lifecycle/releases/tag/v0.15.3 Commits: buildpacks/lifecycle@v0.14.1...v0.15.3 Of note, this resolves the issue seen in v0.15.0 which resulted in the previous upgrade having to be reverted. See: #295 #296 buildpacks/lifecycle#945 buildpacks/lifecycle#946 GUS-W-12037750.
Malax
approved these changes
Jan 18, 2023
heroku-linguist bot
added a commit
that referenced
this pull request
Nov 27, 2024
## 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](https://github.com/heroku/buildpacks-procfile). Those applications must make sure to update their configuration to bind to an IPv6 host. ([#354](heroku/buildpacks-ruby#354)) ### Added - The buildpack now warns the user when environmental variables used in running the default process are not defined. ([#307](heroku/buildpacks-ruby#307))
heroku-linguist bot
added a commit
that referenced
this pull request
Dec 9, 2024
## 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](https://github.com/heroku/buildpacks-procfile). Those applications must make sure to update their configuration to bind to an IPv6 host. ([#354](heroku/buildpacks-ruby#354)) ### Added - The buildpack now warns the user when environmental variables used in running the default process are not defined. ([#307](heroku/buildpacks-ruby#307)) Co-authored-by: heroku-linguist[bot] <136119646+heroku-linguist[bot]@users.noreply.github.com>
heroku-linguist bot
added a commit
that referenced
this pull request
Dec 18, 2024
## heroku/python ### Changed - The build now fails early if known problematic Python and pip-related env vars have been set by the user or earlier buildpacks. ([#308](heroku/buildpacks-python#308)) - The `PIP_PYTHON` env var is now only set at build time. ([#307](heroku/buildpacks-python#307)) ### Removed - Stopped setting the `LANG` env var. ([#306](heroku/buildpacks-python#306)) - Stopped setting the `PYTHONHOME` env var. ([#309](heroku/buildpacks-python#309))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release notes:
https://github.com/buildpacks/lifecycle/releases/tag/v0.14.2
https://github.com/buildpacks/lifecycle/releases/tag/v0.14.3
https://github.com/buildpacks/lifecycle/releases/tag/v0.15.0
https://github.com/buildpacks/lifecycle/releases/tag/v0.15.1
https://github.com/buildpacks/lifecycle/releases/tag/v0.15.2
https://github.com/buildpacks/lifecycle/releases/tag/v0.15.3
Commits:
buildpacks/lifecycle@v0.14.1...v0.15.3
Of note, this:
Regression: processes is not parseable in metadata.toml #295
Revert "Update lifecycle from v0.14.1 to v0.15.0" #296
Regression: processes is not parseable in metadata.toml buildpacks/lifecycle#945
Fix regression in metadata.toml rendering buildpacks/lifecycle#946
GUS-W-12037750.