lifecycle v0.19.0-rc.2

lifecycle v0.19.0-rc.2

Welcome to v0.19.0-rc.2, a 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 (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.19.0-rc.2.

Features

• When using Platform API 0.13 or greater, the exporter accepts a -parallel flag to enable exporting the app image and cache image in parallel (#1247)
• When using Platform API 0.13 or greater, image extensions are no longer experimental (#1295)
• When using Platform API 0.13 or greater, image extensions may write into a shared or specific context directory (#1276)
• Adds support for ppc64le architecture (#1303)
• Documents -image is a deprecated flag (#1304)
• Bumps dependencies (#1226, #1234, #1238, #1259, #1265, #1277, #1279, #1280, #1283, #1281, #1292, #1296)
• Adds debug statements to the extender (#1298)
• Updates go to version 1.21.7

Bugfixes

• The lifecycle will always set CNB_TARGET_* variables during detect, build, and generate (#1309)
• The rebaser when -run-image is not provided will find the run image name in io.buildpacks.lifecycle.metadata instead of performing a no-op (on Platform API 0.12) (#1305)
• The creator errors if the detected group (instead of the order) contains extensions (#1246)
• The exporter zeroes timestamps when adding extension layers to the app image (#1289)
• The extender will successfully copy extended run image layers even if the original run image has a duplicated top layer (#1306)

Library Changes

• Consolidates methods that read and write platform spec'd TOML (#1236)

Full Changelog: v0.18.5...release/0.19.0-rc.2