-
Notifications
You must be signed in to change notification settings - Fork 286
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.
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
Use the lifecycle's Buildpack API Version to determine order.toml format #284
Comments
Signed-off-by: Javier Romero <[email protected]>
Signed-off-by: Javier Romero <[email protected]>
Signed-off-by: Javier Romero <[email protected]>
Seems like we should use the platform API version for order.toml, as it's a contract between the platform and the lifecycle. |
As discussed we'll leave this as is although we understand that it makes more sense to be the Platform API. By using the Buildpack API we can still achieve what we need without needing to bump the Platform API for now and in additional it's technically supported by the lifecycle as-is due to our backwards compatibility efforts in lifecycle itself. |
We should use the lifecycle's Buildpack API Version instead of the lifecycle version now.
Originally posted by @ekcasey in https://github.com/buildpack/pack/diffs/53
The text was updated successfully, but these errors were encountered: