Skip to content

lifecycle v0.19.0

Compare
Choose a tag to compare
@github-actions github-actions released this 07 Mar 18:44
548854f

lifecycle v0.19.0

Welcome to v0.19.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.19.0.

Features

Bugfixes

  • The lifecycle will always set CNB_TARGET_* variables during detect, build, and generate (#1309 by @natalieparellano)
  • 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 by @ryanbrainard)
  • The creator errors if the detected group (instead of the order) contains extensions (#1246 by @natalieparellano)
  • The exporter zeroes timestamps when adding extension layers to the app image (#1289 by @natalieparellano)
  • The extender will successfully copy extended run image layers even if the original run image has a duplicated top layer (#1306 by @natalieparellano)

Library Changes

Full Changelog: v0.18.5...release/0.19.0

Contributors

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

@c0d1ngm0nk3y, @jabrown85, @kritkasahni-google, @loewenstein, @matzew, @modulo11, @natalieparellano, @pbusko, @phil9909, @prashantrewar, @ryanbrainard