This release of the Cloud Native Buildpacks Specification defines Platform API 0.15.

Additions

• Execution Environments: The lifecycle phases (restorer, extender) can utilize CNB_EXEC_ENV. (#416, RFC 0134).
• System Buildpacks: Added support for system.toml (#296, RFC 0101).

This release of the Cloud Native Buildpacks Specification defines Buildpack API 0.12.

Additions

• Execution Environments: Buildpacks can optionally specify supported execution environments (#415, RFC 0134)

This release of the Cloud Native Buildpacks Specification defines Platform API 0.14.

Additions

• The restorer accepts a -run flag (#408)

This release of the Cloud Native Buildpacks Specification defines Platform API 0.13.

Additions

• It is possible to export the app image and cache image in parallel (#380, RFC 0125)
• The lifecycle accepts insecure registries configuration (#385, RFC 0111)
• Image extensions are no longer experimental (#386)
• Image extensions can define the build context directory for build and run base image extension (#384, RFC 0127)

This release of the Cloud Native Buildpacks Specification defines Buildpack API 0.11.

Additions

• Image extensions are no longer experimental (#387)
• Image extensions can define the build context directory for build and run base image extension (#383, RFC 0127)

Breaking Changes

• The lifecycle no longer attempts to maintain compatibility with unsupported Buildpack API 0.2 (#377, RFC 0110)

This release of the Cloud Native Buildpacks Specification defines Platform API 0.12.

Additions

• Image extensions (experimental) can extend the runtime base image (#347, RFC 105)
• OCI layout is a supported export format (#352, RFC 119).
• When selecting a run image, the analyzer and rebaser verify read access (#357).

Breaking Changes

• The concepts of stacks and mixins are removed in favor of existing constructs in the container image ecosystem such as operating system name, operating system version, and architecture (#335, RFC 096).

Nonfunctional Changes

• Clarifies the behavior of user-provided and operator-provided environment variables (#367).

This release of the Cloud Native Buildpacks Specification defines Buildpack API 0.10.

Additions

• Image extensions (experimental) can extend the runtime base image (#353, RFC 105).
• Describe operator-provided vars in build-config directory (#349, RFC 109).

Breaking Changes

• The concepts of stacks and mixins are removed in favor of existing constructs in the container image ecosystem such as operating system name, operating system version, and architecture (#336, RFC 096).

This release of the Cloud Native Buildpacks Specification defines Platform API 0.11.

Additions

• SBOM files for the launcher are included in the exported image within <layers>/sbom/launch; SBOM files for the lifecycle are saved to <layers>/sbom/build; the exporter accepts a -launcher-sbom flag to allow platforms to provide SBOM files for a custom launcher (#332, RFC 0112)
• Platform operators can specify build time environment variables using the /cnb/build-config/env directory (#345, RFC 0109)
• The rebaser accepts a -previous-image flag to allow rebasing by digest reference (#346, RFC 0115)

Nonfunctional Changes

• Adds Buildpack API version to the io.buildpacks.build.metadata label to accurately reflect existing lifecycle behavior (#328)
• Clarifies that <kaniko-dir> is an input to the extender (#329)

This release of the Cloud Native Buildpacks Specification defines Platform API 0.10.

Additions

• The launcher, for newer buildpacks (Buildpack API 0.9 or greater), will override buildpack-provided default arguments with user-provided arguments; it will continue to append user-provided arguments for older buildpacks (#323, RFC 0093)
• The concept of an image extension for base image modification and a new extend lifecycle phase are introduced as experimental components (#319 and #320, RFC 0105)
• When the creator is passed -skip-restore it will still restore store.toml (#324)

Nonfunctional Changes

• “OCI registry” is used instead of “Docker registry” (#310)

This release of the Cloud Native Buildpacks Specification defines Buildpack API 0.9.

Breaking Changes

• Buildpacks may no longer implicitly rely on a shell (buildpack-provided processes are always direct = true) (#305, RFC 0093)

Additions

• The concept of an image extension for base image modification is introduced as an experimental component (#307 and #321, RFC 0105)

Nonfunctional Changes

• Details of the launcher are moved to the platform spec (#305)
• A terminology section is added (#300)
• SVGs are cached and set to white background (so they are visible when using GitHub dark mode) (#315)