lifecycle v0.19.3

lifecycle v0.19.3

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

Features

• N/A

Bugfixes

• Fix keychain bug. Thanks @matejvasek for reporting.

Chores

• update codecov action

Full Changelog: v0.19.2...release/0.19.3

Contributors

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

@natalieparellano @jabrown85

lifecycle v0.19.2

lifecycle v0.19.2

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

Features

• Allow platform operators the ability to skip vendor specific keychain implementations by setting CNB_REGISTRY_AUTH_KEYCHAIN_SKIP_AMAZON or CNB_REGISTRY_AUTH_KEYCHAIN_SKIP_AZURE.

Chores

• Updates go to version 1.22.2

Full Changelog: v0.19.1...release/0.19.2

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.19.1

lifecycle v0.19.1

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

Features

• Bumps google.golang.org/protobuf from 1.32.0 to 1.33.0 (#1318)
• Bumps github.com/docker/docker (#1321)
• Bumps the dependencies group with 4 updates (#1323)

Bugfixes

• Buildpack API 0.11 is supported as of lifecycle 0.19.x (#1326)
• The lifecycle now correctly extracts the target distro name and version from the run image labels io.buildpacks.base.distro.name and io.buildpacks.base.distro.version (#1325)
• Log level and color level are configurable via the environment (#1314)
• Updates README for 0.19.x (#1313)

Full Changelog: v0.19.0...release/0.19.1

lifecycle v0.17.6

lifecycle v0.17.6

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

Features

• Bumps google.golang.org/protobuf from 1.32.0 to 1.33.0
• Bumps github.com/docker/docker

Bugfixes

• The lifecycle now correctly extracts the target distro name and version from the run image labels io.buildpacks.base.distro.name and io.buildpacks.base.distro.version (#1325)

lifecycle v0.17.5

lifecycle v0.17.5

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

Features

• Updates go to version 1.21.8

Bugfixes

• The lifecycle will always set CNB_TARGET_* variables during detect, build, and generate (#1309 by @natalieparellano)

lifecycle v0.19.0

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

• 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 by @kritkasahni-google)
• When using Platform API 0.13 or greater, image extensions are no longer experimental (#1295 by @prashantrewar)
• When using Platform API 0.13 or greater, image extensions may write into a shared or specific context directory (#1276 by @modulo11)
• Adds support for ppc64le architecture (#1303 by @matzew)
• Documents -image is a deprecated flag (#1304 by @ryanbrainard)
• Bumps dependencies (#1226, #1234, #1238, #1259, #1265, #1277, #1279, #1280, #1283, #1281, #1292, #1296, #1310)
• Adds debug statements to the extender (#1298 by @natalieparellano)
• Updates go to version 1.21.8

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

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

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

lifecycle v0.19.0-rc.3

lifecycle v0.19.0-rc.3

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

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 by @kritkasahni-google)
• When using Platform API 0.13 or greater, image extensions are no longer experimental (#1295 by @prashantrewar)
• When using Platform API 0.13 or greater, image extensions may write into a shared or specific context directory (#1276 by @modulo11)
• Adds support for ppc64le architecture (#1303 by @matzew)
• Documents -image is a deprecated flag (#1304 by @ryanbrainard)
• Bumps dependencies (#1226, #1234, #1238, #1259, #1265, #1277, #1279, #1280, #1283, #1281, #1292, #1296, #1310)
• Adds debug statements to the extender (#1298 by @natalieparellano)
• Updates go to version 1.21.8

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

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

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

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

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

lifecycle v0.19.0-rc.1

lifecycle v0.19.0-rc.1

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

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)
• 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 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)

Library Changes

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

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

lifecycle v0.18.5

lifecycle v0.18.5

Welcome to v0.18.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.18.5.

Features

• Bumps dependencies (#1293)
• Updates go to version 1.21.7