Remove CNB_TARGET_*
env vars workaround
#260
Merged
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.
These were added recently in #251 to work around this upstream
lifecycle
bug:buildpacks/lifecycle#1308
The fix for that has since been released in lifecycle 0.19.0:
https://github.com/buildpacks/lifecycle/releases/tag/v0.19.0
Which our builder images are now using:
heroku/cnb-builder-images#475
As such, we no longer need the workaround here (and in fact, setting these env vars now cannot have an effect, since
lifecycle
now ignores them).GUS-W-15225541.