lifecycle v0.17.4

lifecycle v0.17.4

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

Features

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

lifecycle v0.17.3

lifecycle v0.17.3

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

Features

• Updates go to version 1.21.6
• Updates dependencies
• Marks unpatched vulnerability as non-impactful (#1255)

lifecycle v0.18.4

lifecycle v0.18.4

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

Features

• Updates go to version 1.21.6
• Bumps containerd

Full Changelog: v0.18.3...release/0.18.4

lifecycle v0.18.3

lifecycle v0.18.3

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

Features

• Updates golang.org/x/crypto to 0.17.0
• Updates go to version 1.20.12

Full Changelog: v0.18.2...release/0.18.3

Contributors

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

Upgrade golang.org/x/crypto (65f76d6 by @jabrown85)

lifecycle v0.18.2

lifecycle v0.18.2

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

Features

• Bumps dependencies (#1238, #1234, #1226)
• Updates go to version 1.20.11

Full Changelog: v0.18.1...release/0.18.2

lifecycle v0.18.1

lifecycle v0.18.1

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

Bugfixes

• Fixes post-release workflow by capturing the image digest for the linux-s390x image (#1235 by @natalieparellano)

lifecycle v0.18.0

lifecycle v0.18.0

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

Features

• Removes unsupported Buildpack APIs: 0.2, 0.3, 0.4, 0.5, and 0.6 (#1148 by @natalieparellano)
• Removes compatibility layer for unsupported Buildpack APIs (#1188 by @natalieparellano)
• Removes unsupported Platform APIs: 0.3, 0.4, 0.5, and 0.6 (#1191 by @natalieparellano)
• Requires the CNB_PLATFORM_API environment variable to be set (#1145 by @natalieparellano)
• Adds support for s390x architecture (#1142 by @dilipgb)
• Uses keyless signing to cosign sign buildpacksio/lifecycle images in GitHub actions (#1201 by @natalieparellano)
• Reports image name when restorer fails to pull (#1174 by @AidanDelaney)
• Warns when a positional argument might have been a flag (#1147 by @joe-kimmel-vmw)
• Adds explanatory debug logs to the restorer (#1144 by @joe-kimmel-vmw)
• lifecycle now only emits timing to the debug logs (#1230 by @jabrown85)
• Updates go to version 1.20.10

Bugfixes

• Fixes regression in Platform API 0.10 by writing reference in analyzed.toml during the generate phase when the run image was switched by extensions (#1204 by @natalieparellano)
• Fixes access of url based repositories for specific cases (#1222 by @c0d1ngm0nk3y)

Library Changes

• Moves lifecycle package to phase package in sub-directory (#1205 by @natalieparellano)

Full Changelog: v0.17.2...release/0.18.0

Contributors

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

@AidanDelaney, @c0d1ngm0nk3y, @dilipgb, @jabrown85, @jjbustamante, @joe-kimmel-vmw, @natalieparellano

lifecycle v0.18.0-rc.1

lifecycle v0.18.0-rc.1

Welcome to v0.18.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.18.0-rc.1.

Features

• Removes unsupported Buildpack APIs: 0.2, 0.3, 0.4, 0.5, and 0.6 (#1148 by @natalieparellano)
• Removes compatibility layer for unsupported Buildpack APIs (#1188 by @natalieparellano)
• Removes unsupported Platform APIs: 0.3, 0.4, 0.5, and 0.6 (#1191 by @natalieparellano)
• Requires the CNB_PLATFORM_API environment variable to be set (#1145 by @natalieparellano)
• Adds support for s390x architecture (#1142 by @dilipgb)
• Uses keyless signing to cosign sign buildpacksio/lifecycle images in GitHub actions (#1201 by @natalieparellano)
• Reports image name when restorer fails to pull (#1174 by @AidanDelaney)
• Warns when a positional argument might have been a flag (#1147 by @joe-kimmel-vmw)
• Adds explanatory debug logs to the restorer (#1144 by @joe-kimmel-vmw)
• Updates go to version 1.20.10

Bugfixes

• Fixes regression in Platform API 0.10 by writing reference in analyzed.toml during the generate phase when the run image was switched by extensions (#1204 by @natalieparellano)
• Fixes access of url based repositories for specific cases (#1222 by @c0d1ngm0nk3y)

Library Changes

• Moves lifecycle package to phase package in sub-directory (#1205 by @natalieparellano)

Full Changelog: v0.17.1...release/0.18.0-rc.1

Contributors

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

@AidanDelaney, @c0d1ngm0nk3y, @dilipgb, @jabrown85, @jjbustamante, @joe-kimmel-vmw, @natalieparellano

lifecycle v0.17.2

lifecycle v0.17.2

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

Features

• Bumps golang.org/x/net (#1223 by @natalieparellano)
• Updates go to version 1.20.10

lifecycle v0.17.1

lifecycle v0.17.1

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

Features

• Updates go to version 1.20.8

Bugfixes

• Adds missing flags for OCI layout to restorer (#1195 by @jjbustamante )
• Removes erroneous log line Ignoring cache image "<cache image name>" because it was corrupt (#1185 by @natalieparellano)