Javier Romero

We should be able to simply use the platform API version to determine the execution order. - Migration and features enabled by this are separate to this issue.

Given that this is associated with ARM could you provide the specific configuration you're wishing to be possible? Here's a "matrix" of all the components and how they interact. It...

Hi @Extant-1, just following up on this. Did you ever figure out what may be happening here?

## Additional Resources * [RFC Pull Request](https://github.com/buildpacks/rfcs/pull/9) (conversations behind idea) * [Accepted RFC](https://github.com/buildpacks/rfcs/blob/main/text/0013-app-layer-metadata-source.md) (accepted idea) * Spec Changes: * [Draft](https://github.com/buildpacks/spec/pull/68/files) * [Final](https://github.com/buildpacks/spec/pull/81/files) **NOTE: RFC details may change as the move...

#524 may be able to assist with the first bullet point here if the non-daemon case is used.

> @jromero why not add templates for new APIs in advance of support in all suggested builders? Users can still choose an older API template right? Not sure I understand...

There are a couple things we'd probably want to hash out through an RFC process: 1. We should aim to use the same flag for any source input. If `--path`...

> However, I couldn't find any documentation that explains that api field should be set in buildpack.toml Created buildpack/docs#66 to address this. > If such documentation exists or is later...

Recording the `sha` for the build image at the creation of `builder` makes sense. For run images, the intent is that run images are updated after a builder is created....

> Hi folks! I've made a barebones BuildKit frontend (available [here](https://github.com/EricHripko/cnbp)). It's doesn't offer the full functionality/spec compatibility, but would love to hear your feedback 🙂 This is great! Thanks...