lifecycle v0.20.0

lifecycle v0.20.0

Welcome to v0.20.0, a 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 (compatible) daemon or an OCI registry.

Install

Extract the .tgz file and copy the lifecycle binaries into a build 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.20.0.

Features

• The lifecycle, when encountering cache metadata for a layer that does not exist in the cache, will skip over the layer instead of failing the build (#1381 by @joeybrown-sf)
• When using Platform API 0.14 or greater, the restorer restores cached launch layers even if they are not found in the previous image (#1346 by @pbusko)
• When using Platform API 0.14 or greater, the restorer ensures read access to the run image selected by extensions (#1364 by @pbusko)
• The lifecycle surfaces the error from the registry (when it fails to verify image permissions) as an error instead of a debug message (#1376 by @natalieparellano)
• Bumps dependencies (#1375 and #1373)
• Updates go to version 1.22.5

Bugfixes

• The lifecycle, when populating target data for older platforms, populates OS & architecture as well as distro information (#1374 by @natalieparellano)

Full Changelog: v0.19.7...release/0.20.0

Contributors

We'd like to acknowledge that this release wouldn't be as good without the help of the following amazing contributors:

@edmorley, @jabrown85, @joeybrown-sf, @natalieparellano, @pbusko