lifecycle v0.20.4

lifecycle v0.20.4

Welcome to v0.20.4, 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.4.

Features

• Improve corrupted cache handling (@natalieparellano #1410 )

Chores

• Updates go to version 1.23.3
• Bump github actions (@jabrown85 #1419 )

Full Changelog: v0.20.3...release/0.20.4

Contributors

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

@joeybrown-sf @natalieparellano @jabrown85

lifecycle v0.20.3

lifecycle v0.20.3

Welcome to v0.20.3, 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.3.

Features

• Updates go to version 1.22.8

Bugfixes

Chores

Full Changelog: v0.20.2...release/0.20.3

Contributors

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

@jabrown85 @natalieparellano

lifecycle v0.20.2

lifecycle v0.20.2

Welcome to v0.20.2, 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.2.

Features

• Updates go to version 1.22.7

Bugfixes

• Adjust exporter App Layer log output (#1399)

Full Changelog: v0.20.1...release/0.20.2

Contributors

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

@natalieparellano @jabrown85

v0.20.1

lifecycle v0.20.1

Welcome to v0.20.1, 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.1.

Features

Bugfixes

• Fix run-image access check in restorer phase (#1386 by @pbusko and @nicolasbender )
• When setting up buildpack env, process layers for a given buildpack in alphabetical order (#1394 by @natalieparellano)

Chores

• Updates go to version 1.22.6
• #1390 docker from 26.1.4+incompatible to 26.1.5+incompatible
• #1384 Adapt tools/test-fork/sh to current GitHub Actions workflows

Full Changelog: v0.20.0...release/0.20.1

Contributors

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

@pbusko @nicolasbender @natalieparellano @jabrown85 @hhiroshell

lifecycle v0.17.7

lifecycle v0.17.7

Welcome to v0.17.7, 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 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.17.7.

Features

• Bumps imgutil and docker (5b1f05e)
• Updates go to version 1.21.12

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

lifecycle v0.19.7

lifecycle v0.19.7

Welcome to v0.19.7, 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.7.

Features

• Updates dependencies (#1360 by @dependabot)
• Updates go to version 1.22.4

Bugfixes

• Bumps imgutil to pick up fixes for containerd and podman (#1361 by @natalieparellano)

Full Changelog: v0.19.6...release/0.19.7

lifecycle v0.19.6

lifecycle v0.19.6

Welcome to v0.19.6, 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.6.

Bugfixes

• More fixes for target compat checking during detect (#1354 by @natalieparellano)

Full Changelog: v0.19.5...release/0.19.6

lifecycle v0.19.5

lifecycle v0.19.5

Welcome to v0.19.5, 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.5.

Bugfixes

• The detector, when determining if a base image satisfies target constraints declared by a buildpack, also uses information from /etc/os-release when distro information is not present in the run image labels (#1352 by @natalieparellano)

Full Changelog: v0.19.4...release/0.19.5

lifecycle v0.19.4

lifecycle v0.19.4

Welcome to v0.19.4, 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.4.

Features

• Bumps dependencies (#1335, #1343, #1349, #1351)
• Updates go to version 1.22.3

Bugfixes

• The lifecycle, when finding run image target information, will fall back to reading /etc/os-release when distro information is not present in the run image labels (#1347 by @pbusko)
• The lifecycle, when determining if a base image satisfies target constraints declared by a buildpack, fails if the buildpack declares distro information but the base image does not (fixes spec compliance) (#1348 by @natalieparellano)

Library Changes

• The restorer initializes a default LayerMetadataRestorer and SBOMRestorer if none is provided (#1333 by @pbusko)

Full Changelog: v0.19.3...release/0.19.4

Contributors

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

@c0d1ngm0nk3y, @edmorley, @jabrown85, @natalieparellano, @pbusko