lifecycle v0.17.0

lifecycle v0.17.0

Welcome to v0.17.0, a beta 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.0.

Features

• When using platform API 0.12 or greater, the lifecycle validates “targets” instead of stacks (#994, #1030, #1050, #1053, #1064 by @joe-kimmel-vmw, #1056 by @jabrown85, #1005 by @natalieparellano)
• (Experimental) When using platform API 0.12 or greater, the lifecycle supports run image extension with Dockerfiles, in addition to run image switching (#1011, #1014, #1022, #1055, #1134 by @natalieparellano, #1032 by @jabrown85)
• (Experimental) When using platform API 0.12 or greater, the lifecycle supports export to OCI layout format on disk (#969 by @jjbustamante)
• When selecting a run image, the analyzer and rebaser verify read access (#1024 by @pbusko, @c0d1ngm0nk3y, @modulo11, and @kulhadia)
• The analyzer validates that the cache image and previous image are valid (#1060 by @matthewrobertson)
• When using platform API 0.12 or greater, the exporter includes history in the application image (#1099 by @natalieparellano)
• When using platform API 0.12 or greater, the rebaser will fail if the provided run image is not found in the io.buildpacks.lifecycle.metadata label, unless --force is passed; if --force is passed, it overrides the existing run image and run image mirrors information (#1104, #1132 by @natalieparellano)
• The lifecycle when checking read/write access to images will surface the error if there are no images to fallback to (#1133 by @natalieparellano)
• Updates go to version 1.20.7

Bugfixes

• The restorer accepts a -layers flag again (#1143 by @joe-kimmel-vmw)

Chores

• buildpack.DecodeLayerMetadataFile() accepts a logger instead of returning a message (#1038 by @anushkamittal20)
• Add layer metadata test as living doc (#1019 by @AidanDelaney)
• Make a single constructor for lifecycle inputs (#1009 by @natalieparellano)
• Replaces deprecated GHA ::set-output syntax (#1037 by @phil9909)

Full Changelog: v0.16.5...release/0.17.0

Contributors

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

@AidanDelaney, @anushkamittal20, @c0d1ngm0nk3y, @hernandanielg, @jabrown85, @jjbustamante, @joe-kimmel-vmw, @kulhadia, @matthewrobertson, @modulo11, @natalieparellano, @pbusko, @phil9909

lifecycle v0.17.0-rc.4

lifecycle v0.17.0-rc.4

Welcome to v0.17.0-rc.4, a beta 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 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.0-rc.4.

Features

• When using platform API 0.12 or greater, the lifecycle validates “targets” instead of stacks (#994, #1030, #1050, #1053, #1064 by @joe-kimmel-vmw, #1056 by @jabrown85, #1005 by @natalieparellano)
• (Experimental) When using platform API 0.12 or greater, the lifecycle supports run image extension with Dockerfiles, in addition to run image switching (#1011, #1014, #1022, #1055, #1134 by @natalieparellano, #1032 by @jabrown85)
• (Experimental) When using platform API 0.12 or greater, the lifecycle supports export to OCI layout format on disk (#969 by @jjbustamante)
• When selecting a run image, the analyzer and rebaser verify read access (#1024 by @pbusko, @c0d1ngm0nk3y, @modulo11, and @kulhadia)
• The analyzer validates that the cache image and previous image are valid (#1060 by @matthewrobertson)
• When using platform API 0.12 or greater, the exporter includes history in the application image (#1099 by @natalieparellano)
• When using platform API 0.12 or greater, the rebaser will fail if the provided run image is not found in the io.buildpacks.lifecycle.metadata label, unless --force is passed; if --force is passed, it overrides the existing run image and run image mirrors information (#1104, #1132 by @natalieparellano)
• The lifecycle when checking read/write access to images will surface the error if there are no images to fallback to (#1133 by @natalieparellano)
• Updates go to version 1.20.7

Bugfixes

• The restorer accepts a -layers flag again (#1143 by @joe-kimmel-vmw)

Chores

• buildpack.DecodeLayerMetadataFile() accepts a logger instead of returning a message (#1038 by @anushkamittal20)
• Add layer metadata test as living doc (#1019 by @AidanDelaney)
• Make a single constructor for lifecycle inputs (#1009 by @natalieparellano)
• Replaces deprecated GHA ::set-output syntax (#1037 by @phil9909)

Full Changelog: v0.16.5...release/0.17.0-rc.4

Contributors

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

@AidanDelaney, @anushkamittal20, @c0d1ngm0nk3y, @hernandanielg, @jabrown85, @jjbustamante, @joe-kimmel-vmw, @kulhadia, @matthewrobertson, @modulo11, @natalieparellano, @pbusko, @phil9909

lifecycle v0.16.5

lifecycle v0.16.5

Welcome to v0.16.5, a beta 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.16.5.

Features

• updates to go 1.19.11

lifecycle v0.17.0-rc.3

lifecycle v0.17.0-rc.3

Welcome to v0.17.0-rc.3, a beta 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 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.0-rc.3.

Features

• When using platform API 0.12 or greater, the lifecycle validates “targets” instead of stacks (#994, #1030, #1050, #1053, #1064 by @joe-kimmel-vmw, #1056 by @jabrown85, #1005 by @natalieparellano)
• (Experimental) When using platform API 0.12 or greater, the lifecycle supports run image extension with Dockerfiles, in addition to run image switching (#1011, #1014, #1022, #1055 by @natalieparellano, #1032 by @jabrown85)
• (Experimental) When using platform API 0.12 or greater, the lifecycle supports export to OCI layout format on disk (#969 by @jjbustamante)
• When selecting a run image, the analyzer and rebaser verify read access (#1024 by @pbusko, @c0d1ngm0nk3y, @modulo11, and @kulhadia)
• The analyzer validates the cache image and previous image are valid (#1060 by @matthewrobertson)
• When using platform API 0.12 or greater, the exporter includes history in the application image (#1099 by @natalieparellano)
• When using platform API 0.12 or greater, the rebaser will fail if the provided run image is not found in the io.buildpacks.lifecycle.metadata label, unless --force is passed; if --force is passed, it overrides the existing run image and run image mirrors information (#1104, #1132 by @natalieparellano)
• The lifecycle when checking read/write access to images will surface the error if there are no images to fallback to (#1133 by @natalieparellano)
• Updates go to version 1.20.5 (#1130 by @natalieparellano)
• Fixes for run image extension (#1134 by @natalieparellano )
  • When pulling remote image data, fail if the remote image is not found
  • When validating dockerfiles, set extend to true if there are any instructions (vs more than one instruction)
  • Update matching logic when considering if two image names are equivalent to ignore the digest portion of the reference if present (for the purpose of selecting data from run.toml to add to the lifecycle metadata label i.e., “run image for rebase”)
  • When exporting, continue to use run image identifier (which could be a digest reference or daemon image ID)
    instead of falling back to image name when exporting to a daemon.
  • When finding the run image info for export, use the run image "image" (name)
    in analyzed.toml as the search key
  • Fix: use "image" instead of "reference" and also guard against image not found
    when we are only updating the reference and target data in analyzed.toml

Chores

• buildpack.DecodeLayerMetadataFile() accepts a logger instead of returning a message (#1038 by @anushkamittal20)
• Add layer metadata test as living doc (#1019 by @AidanDelaney)
• Make a single constructor for lifecycle inputs (#1009 by @natalieparellano)

Full Changelog: v0.16.0...release/0.17.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:

@AidanDelaney, @anushkamittal20, @c0d1ngm0nk3y, @hernandanielg, @jabrown85, @jjbustamante, @joe-kimmel-vmw, @kulhadia, @matthewrobertson, @modulo11, @natalieparellano, @pbusko

lifecycle v0.17.0-rc.2

lifecycle v0.17.0-rc.2

Welcome to v0.17.0-rc.2, a beta 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 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.0-rc.2.

Features

• When using platform API 0.12 or greater, the lifecycle validates “targets” instead of stacks (#994, #1030, #1050, #1053, #1064 by @joe-kimmel-vmw, #1056 by @jabrown85, #1005 by @natalieparellano)
• (Experimental) When using platform API 0.12 or greater, the lifecycle supports run image extension with Dockerfiles, in addition to run image switching (#1011, #1014, #1022, #1055 by @natalieparellano, #1032 by @jabrown85)
• (Experimental) When using platform API 0.12 or greater, the lifecycle supports export to OCI layout format on disk (#969 by @jjbustamante)
• When selecting a run image, the analyzer and rebaser verify read access (#1024 by @pbusko, @c0d1ngm0nk3y, @modulo11, and @kulhadia)
• The analyzer validates the cache image and previous image are valid (#1060 by @matthewrobertson)
• When using platform API 0.12 or greater, the exporter includes history in the application image (#1099 by @natalieparellano)
• When using platform API 0.12 or greater, the rebaser will fail if the provided run image is not found in the io.buildpacks.lifecycle.metadata label, unless --force is passed; if --force is passed, it overrides the existing run image and run image mirrors information (#1104, #1132 by @natalieparellano)
• The lifecycle when checking read/write access to images will surface the error if there are no images to fallback to (#1133 by @natalieparellano)
• Updates go to version 1.20.5 (#1130 by @natalieparellano)

Chores

• buildpack.DecodeLayerMetadataFile() accepts a logger instead of returning a message (#1038 by @anushkamittal20)
• Add layer metadata test as living doc (#1019 by @AidanDelaney)
• Make a single constructor for lifecycle inputs (#1009 by @natalieparellano)

Full Changelog: v0.16.0...v0.17.0-rc.2

Contributors

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

@AidanDelaney, @anushkamittal20, @c0d1ngm0nk3y, @hernandanielg, @jabrown85, @jjbustamante, @joe-kimmel-vmw, @kulhadia, @matthewrobertson, @modulo11, @natalieparellano, @pbusko

lifecycle v0.17.0-rc.1

lifecycle v0.17.0-rc.1

Welcome to v0.17.0-rc.1, a beta 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 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.0-rc.1.

Features

• When using platform API 0.12 or greater, the lifecycle validates “targets” instead of stacks (#994, #1030, #1050, #1053, #1064 by @joe-kimmel-vmw, #1056 by @jabrown85, #1005 by @natalieparellano)
• (Experimental) When using platform API 0.12 or greater, the lifecycle supports run image extension with Dockerfiles, in addition to run image switching (#1011, #1014, #1022, #1055 by @natalieparellano, #1032 by @jabrown85)
• (Experimental) When using platform API 0.12 or greater, the lifecycle supports export to OCI layout format on disk (#969 by @jjbustamante)
• When selecting a run image, the analyzer and rebaser verify read access (#1024 by @pbusko, @c0d1ngm0nk3y, @modulo11, and @kulhadia)
• The analyzer validates the cache image and previous image are valid (#1060 by @matthewrobertson)
• When using platform API 0.12 or greater, the exporter includes history in the application image (#1099 by @natalieparellano)
• When rebasing images built with platform API 0.12 or greater, the rebaser overrides run image and run image mirrors information in the io.buildpacks.lifecycle.metadata label when the new run image reference is not already contained there (#1104 by @natalieparellano)
• Updates go to version 1.20.5 (#1130 by @natalieparellano)

Chores

• buildpack.DecodeLayerMetadataFile() accepts a logger instead of returning a message (#1038 by @anushkamittal20)
• Add layer metadata test as living doc (#1019 by @AidanDelaney)
• Make a single constructor for lifecycle inputs (#1009 by @natalieparellano)

Full Changelog: v0.16.0...v0.17.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, @anushkamittal20, @c0d1ngm0nk3y, @hernandanielg, @jabrown85, @jjbustamante, @joe-kimmel-vmw, @kulhadia, @matthewrobertson, @modulo11, @natalieparellano, @pbusko

lifecycle v0.16.4

lifecycle v0.16.4

Welcome to v0.16.4, a beta 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.16.4.

Features

• Updates go to version 1.19.10

lifecycle v0.17.0-pre.2

lifecycle v0.17.0-pre.2

Welcome to v0.17.0-pre.2, a beta 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 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.0-pre.2.

Features

This minor version is a work-in-progress - please open an issue or comment here to report issues
In v0.17.0-pre.2 you get everything in v0.17.0-pre1 AND ...

• improved OS inference for multi-OS buildpacks
• run image extensions have the final say on their own run image references
• we bumped some dependencies (you won't believe which was fourth!)
• analyzer validates cache and previous image
• we only select run-image mirrors that we can definitely read from
• lifecycle should now populate the CNB_TARGET_* environment variables
• ... and more!

lifecycle v0.16.3

lifecycle v0.16.3

Welcome to v0.16.3, a beta 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.16.3.

Features

• Updates go to version 1.19.9

lifecycle v0.16.2

lifecycle v0.16.2

Welcome to v0.16.2, a beta 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.16.2.

Features

• Updates go to version 1.19.8
• Bump github.com/docker/docker from v23.0.1 to v23.0.4
• Bump github.com/moby/buildkit from 0.11.4 to v0.11.5
• Bump golang.org/x/sys from 0.6.0 to v0.7.0
• Bump github.com/opencontainers/runc to from v1.1.4 to v.1.1.7
• Bump google.golang.org/protobuf from v1.29.0 to v1.29.1