lifecycle v0.13.1

lifecycle v0.13.1

Welcome to v0.13.1, a beta 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.13.1.

Features

• Updates ggcr to version 0.7.0 (#774)
• Updates docker to version 20.10.11+incompatible (#769)

Bug Fixes

• For launch=true cache=false layers, layer sbom files are included in the exported image on second (and subsequent) builds (#773 by @natalieparellano)
• For launch=false cache=true layers, when using a cache directory, layer sbom files are restored from the cache and are included in /layers/sbom/build (#773 by @natalieparellano)
• For second (and subsequent) builds, when the creator is run with -skip-restore, /layers/sbom is cleared before the build phase, to avoid pollution from sboms for undetected buildpacks (#773 by @natalieparellano)
• The creator keeps daemon connection open using ping during build phase, to fix timeout errors when using podman (#684 by @matejvasek)
• Better error message when daemon connection is called in parallel (#779 by @matejvasek)

Chores

• The layer metadata restorer and the layer sha store are moved to an internal package (#724 by @yaelharel)

Contributors

We'd like to acknowledge that this release wouldn't be as good without the help of the following amazing contributors:
@aemengo, @jabrown85, @matejvasek, @natalieparellano, @yaelharel