lifecycle v0.14.0-rc.1

lifecycle v0.14.0-rc.1

Welcome to v0.14.0-rc.1, a beta pre-release of the Cloud Native Buildpacks Lifecycle.

Prerequisites

The lifecycle runs as a normal user in a series of unprivileged containers. To export images and cache image layers, it requires access to a Docker daemon or Docker registry.

Install

Extract the .tgz file and copy the lifecycle binaries into a build stack base image. The build image can then be orchestrated by a platform implementation such as the pack CLI or tekton.

Lifecycle Image

An OCI image containing the lifecycle binaries is available at buildpacksio/lifecycle:0.14.0-rc.1.

Features

• When using buildpack API 0.8 or greater, buildpacks can specify the working directory for processes in launch.toml (#792 by @mboldt)
• When using buildpack API 0.8 or greater, the platform directory and build plan path are provided as environment variables to buildpack bin/detect, in addition to the deprecated positional arguments (#818 by @mboldt)
• When using buildpack API 0.8 or greater, the platform directory, buildpack plan path, and buildpack layers directory are provided as environment variables to buildpack bin/build, in addition to the deprecated positional arguments (#818 by @mboldt)
• The exporter, if SOURCE_DATE_EPOCH is set in its environment, will set image create time to the provided value instead of the constant January 1, 1980 (#823 by @natalieparellano)
• When using platform API 0.9 or greater, the exporter will omit legacy BOM information from the io.buildpacks.build.metadata label; this information can instead be found in /sbom/launch/sbom.legacy.json (#825 by @natalieparellano)

Bug Fixes

• The builder, when validating buildpack-output SBOM files against buildpack-declared SBOM formats, will omit optional parameters in the declared media type from the comparison, allowing buildpacks to specify parameters in buildpack.toml (#834 by @natalieparellano)
• When using platform API 0.9 or greater, the analyzer accepts a -launch-cache flag, improving performance when restoring the SBOM layer from the previous image; additionally, the analyzer accepts a -skip-layers flag to completely skip SBOM layer restoration (#800 by @natalieparellano)