This guide describes changes from platform API 0.3 to 0.4, who these changes are relevant for, as well as any actions that may be necessary.
This guide is most relevant to platform operators.
See the spec release for platform API 0.4 for the full list of changes and further details.
Windows image builds are now supported! See the Windows build guide for more details.
When running the exported application image, it is now possible to provide arguments to pre-defined process types.
The new flow is described here.
As part of these changes, the exporter will not set, and the launcher no longer accepts, the
See the associated RFC and spec PR
for more details.
The exporter and rebaser now produce a report.toml containing the identifier of the application image. When building, platforms can optionally specify the location of the report, or save it off somewhere.
When interpreting the Bill-of-Materials (BOM),
version will no longer be found at the top level.
The lifecycle will convert any
version provided by buildpacks to
Related: as of buildpack API 0.3,
version is deprecated as a top-level key in the build plan.
The lifecycle now defines specific error codes to signal the lifecycle phase where the error occurred, and for API incompatibilities.
When building, the new error codes can be interpreted according to the new definition.
This is particularly helpful when using the