Reintroduce stacks into buildpack.toml for compatibility with pack #251
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
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.
Our publish automation is broken as can be seen here. The issue is described in buildpacks/pack#2047, but basically
pack buildpack packagewill error without a[[stacks]]key. This has been fixed in buildpacks/pack#2081, but it has not yet been released.This change reintroduces
stacksintobuildpack.tomlso thatpack buildpack packagewill work on this buildpack again. This is the same fix we applied in heroku/buildpacks-procfile#210.