-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add support for buildpacks API 0.10 #260
Comments
Doesn't it need to be about 0.8 -> 0.9 -> 0.10, i.e. using https://buildpacks.io/docs/reference/spec/migration/buildpack-api-0.8-0.9/ and then https://buildpacks.io/docs/reference/spec/migration/buildpack-api-0.9-0.10/? |
Could you provide more details for these subtasks, please? We haven't found any relevant changes from 0.9 -> 0.10 affecting libcnb. |
@loewenstein 0.9 is already supported, so we just need to add 0.10 support. It needs to be an additive change.
In a nutshell, breaking API changes. We reworked the core build/detect mechanism. It was previously done with structs at its heart, and we changed it to be function-based now. I believe it'll be more flexible, but this was also done in conjunction with the Paketo team to position them to be able to use libcnb as the base for their packit library. Aside from that, we made some changes to the way logging works as well, so it's more pluggable. We've removed some other cruft like old buildpack API compatibility. We've fixed some other minor annoyances in the APIs as well. |
Is libcnb supposed to support authoring extensions? |
But why wasn't |
v1 supports 0.8. That is the highest it will ever go because going above that requires breaking API changes. https://github.com/buildpacks/libcnb/blob/release-1.x/build.go#L95-L99 Yes, we support extensions in v2. There are a couple under Paketo Community using it, but we haven't had a huge demand for it. I was hoping that it would stabilize more before we release libcnb v2 and it looks like it has so that's another milestone complete towards v2 release. |
This could probably be broken down into more tasks, but at a high level we need to add support for 0.10.
https://buildpacks.io/docs/reference/spec/migration/buildpack-api-0.9-0.10/
The text was updated successfully, but these errors were encountered: