renovate[bot]
commented
4 months ago ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):
- 25 additional dependencies were updated
Details:
| Package | Change |
|---|---|
cloud.google.com/go/pubsub |
v1.36.1 -> v1.37.0 |
cloud.google.com/go/storage |
v1.38.0 -> v1.39.1 |
github.com/BurntSushi/toml |
v1.3.2 -> v1.4.0 |
github.com/google/go-containerregistry |
v0.19.0 -> v0.20.0 |
github.com/hashicorp/go-retryablehttp |
v0.7.2 -> v0.7.5 |
golang.org/x/oauth2 |
v0.18.0 -> v0.20.0 |
google.golang.org/api |
v0.169.0 -> v0.170.0 |
cloud.google.com/go/compute/metadata |
v0.2.3 -> v0.3.0 |
github.com/moby/buildkit |
v0.12.5 -> v0.13.2 |
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp |
v0.49.0 -> v0.50.0 |
go.opentelemetry.io/otel |
v1.24.0 -> v1.25.0 |
go.opentelemetry.io/otel/metric |
v1.24.0 -> v1.25.0 |
go.opentelemetry.io/otel/trace |
v1.24.0 -> v1.25.0 |
google.golang.org/genproto/googleapis/api |
v0.0.0-20240318140521-94a12d6c2237 -> v0.0.0-20240325203815-454cdb8f5daa |
google.golang.org/genproto/googleapis/rpc |
v0.0.0-20240318140521-94a12d6c2237 -> v0.0.0-20240521202816-d264139d666e |
cloud.google.com/go |
v0.112.1 -> v0.112.2 |
cloud.google.com/go/iam |
v1.1.6 -> v1.1.7 |
github.com/buildpacks/imgutil |
v0.0.0-20230919143643-4ec9360d5f02 -> v0.0.0-20240605145725-186f89b2d168 |
github.com/containerd/stargz-snapshotter/estargz |
v0.14.3 -> v0.15.1 |
github.com/docker/docker-credential-helpers |
v0.8.0 -> v0.8.1 |
github.com/googleapis/gax-go/v2 |
v2.12.2 -> v2.12.3 |
github.com/prometheus/client_golang |
v1.17.0 -> v1.19.0 |
github.com/prometheus/common |
v0.44.0 -> v0.48.0 |
google.golang.org/genproto |
v0.0.0-20240213162025-012b6fc9bca9 -> v0.0.0-20240401170217-c3f982113cda |
google.golang.org/protobuf |
v1.33.0 -> v1.34.1 |
sonarcloud[bot]
This PR contains the following updates:
v0.18.5->v0.20.3Release Notes
buildpacks/lifecycle (github.com/buildpacks/lifecycle)
### [`v0.20.3`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.20.3): lifecycle v0.20.3 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.20.2...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### 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**: https://github.com/buildpacks/lifecycle/compare/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](https://redirect.github.com/jabrown85) [@natalieparellano](https://redirect.github.com/natalieparellano) ### [`v0.20.2`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.20.2): lifecycle v0.20.2 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.20.1...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### 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 ([https://github.com/buildpacks/lifecycle/pull/1399](https://redirect.github.com/buildpacks/lifecycle/pull/1399)) **Full Changelog**: https://github.com/buildpacks/lifecycle/compare/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](https://redirect.github.com/natalieparellano) [@jabrown85](https://redirect.github.com/jabrown85) ### [`v0.20.1`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.20.1) [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.20.0...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### 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](https://redirect.github.com/buildpacks/lifecycle/issues/1386) by [@pbusko](https://redirect.github.com/pbusko) and [@nicolasbender](https://redirect.github.com/nicolasbender) ) - When setting up buildpack env, process layers for a given buildpack in alphabetical order ([#1394](https://redirect.github.com/buildpacks/lifecycle/issues/1394) by [@natalieparellano](https://redirect.github.com/natalieparellano)) #### Chores - Updates go to version 1.22.6 - [#1390](https://redirect.github.com/buildpacks/lifecycle/issues/1390) docker from 26.1.4+incompatible to 26.1.5+incompatible - [#1384](https://redirect.github.com/buildpacks/lifecycle/issues/1384) Adapt tools/test-fork/sh to current GitHub Actions workflows **Full Changelog**: https://github.com/buildpacks/lifecycle/compare/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](https://redirect.github.com/pbusko) [@nicolasbender](https://redirect.github.com/nicolasbender) [@natalieparellano](https://redirect.github.com/natalieparellano) [@jabrown85](https://redirect.github.com/jabrown85) [@hhiroshell](https://redirect.github.com/hhiroshell) ### [`v0.20.0`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.20.0): lifecycle v0.20.0 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.19.7...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### 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](https://redirect.github.com/buildpacks/lifecycle/issues/1381) by [@joeybrown-sf](https://redirect.github.com/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](https://redirect.github.com/buildpacks/lifecycle/issues/1346) by [@pbusko](https://redirect.github.com/pbusko)) - When using Platform API 0.14 or greater, the `restorer` ensures read access to the run image selected by extensions ([#1364](https://redirect.github.com/buildpacks/lifecycle/issues/1364) by [@pbusko](https://redirect.github.com/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](https://redirect.github.com/buildpacks/lifecycle/issues/1376) by [@natalieparellano](https://redirect.github.com/natalieparellano)) - Bumps dependencies ([#1375](https://redirect.github.com/buildpacks/lifecycle/issues/1375) and [#1373](https://redirect.github.com/buildpacks/lifecycle/issues/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](https://redirect.github.com/buildpacks/lifecycle/issues/1374) by [@natalieparellano](https://redirect.github.com/natalieparellano)) **Full Changelog**: https://github.com/buildpacks/lifecycle/compare/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](https://redirect.github.com/edmorley), [@jabrown85](https://redirect.github.com/jabrown85), [@joeybrown-sf](https://redirect.github.com/joeybrown-sf), [@natalieparellano](https://redirect.github.com/natalieparellano), [@pbusko](https://redirect.github.com/pbusko) ### [`v0.19.7`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.19.7): lifecycle v0.19.7 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.19.6...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### Lifecycle Image An OCI image containing the lifecycle binaries is available at `buildpacksio/lifecycle:0.19.7`. #### Features - Updates dependencies ([#1360](https://redirect.github.com/buildpacks/lifecycle/issues/1360) by [@dependabot](https://redirect.github.com/dependabot)) - Updates go to version 1.22.4 #### Bugfixes - Bumps imgutil to pick up fixes for containerd and podman ([#1361](https://redirect.github.com/buildpacks/lifecycle/issues/1361) by [@natalieparellano](https://redirect.github.com/natalieparellano)) **Full Changelog**: https://github.com/buildpacks/lifecycle/compare/v0.19.6...release/0.19.7 ### [`v0.19.6`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.19.6): lifecycle v0.19.6 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.19.5...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### 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 ([https://github.com/buildpacks/lifecycle/pull/1354](https://redirect.github.com/buildpacks/lifecycle/pull/1354) by [@natalieparellano](https://redirect.github.com/natalieparellano)) **Full Changelog**: https://github.com/buildpacks/lifecycle/compare/v0.19.5...release/0.19.6 ### [`v0.19.5`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.19.5): lifecycle v0.19.5 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.19.4...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### 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 ([https://github.com/buildpacks/lifecycle/pull/1352](https://redirect.github.com/buildpacks/lifecycle/pull/1352) by [@natalieparellano](https://redirect.github.com/natalieparellano)) **Full Changelog**: https://github.com/buildpacks/lifecycle/compare/v0.19.4...release/0.19.5 ### [`v0.19.4`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.19.4): lifecycle v0.19.4 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.19.3...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### Lifecycle Image An OCI image containing the lifecycle binaries is available at `buildpacksio/lifecycle:0.19.4`. #### Features - Bumps dependencies ([#1335](https://redirect.github.com/buildpacks/lifecycle/issues/1335), [#1343](https://redirect.github.com/buildpacks/lifecycle/issues/1343), [#1349](https://redirect.github.com/buildpacks/lifecycle/issues/1349), [#1351](https://redirect.github.com/buildpacks/lifecycle/issues/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](https://redirect.github.com/buildpacks/lifecycle/issues/1347) by [@pbusko](https://redirect.github.com/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](https://redirect.github.com/buildpacks/lifecycle/issues/1348) by [@natalieparellano](https://redirect.github.com/natalieparellano)) #### Library Changes - The restorer initializes a default LayerMetadataRestorer and SBOMRestorer if none is provided ([#1333](https://redirect.github.com/buildpacks/lifecycle/issues/1333) by [@pbusko](https://redirect.github.com/pbusko)) **Full Changelog**: https://github.com/buildpacks/lifecycle/compare/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](https://redirect.github.com/c0d1ngm0nk3y), [@edmorley](https://redirect.github.com/edmorley), [@jabrown85](https://redirect.github.com/jabrown85), [@natalieparellano](https://redirect.github.com/natalieparellano), [@pbusko](https://redirect.github.com/pbusko) ### [`v0.19.3`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.19.3): lifecycle v0.19.3 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.19.2...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### Lifecycle Image An OCI image containing the lifecycle binaries is available at buildpacksio/lifecycle:0.19.3. #### Features - N/A #### Bugfixes - Fix [keychain bug](https://redirect.github.com/buildpacks/lifecycle/commit/267025743f10e892399457dd7df4e5e97f0c342b). Thanks [@matejvasek](https://redirect.github.com/matejvasek) for reporting. #### Chores - [update codecov action](https://redirect.github.com/buildpacks/lifecycle/commit/ecbcbd94d456cea2a39217d6bfaa24db90c35108) **Full Changelog**: https://github.com/buildpacks/lifecycle/compare/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](https://redirect.github.com/natalieparellano) [@jabrown85](https://redirect.github.com/jabrown85) ### [`v0.19.2`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.19.2): lifecycle v0.19.2 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.19.1...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### 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**: https://github.com/buildpacks/lifecycle/compare/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](https://redirect.github.com/jabrown85) [@natalieparellano](https://redirect.github.com/natalieparellano) ### [`v0.19.1`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.19.1): lifecycle v0.19.1 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.19.0...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### 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](https://redirect.github.com/buildpacks/lifecycle/issues/1318)) - Bumps github.com/docker/docker ([#1321](https://redirect.github.com/buildpacks/lifecycle/issues/1321)) - Bumps the dependencies group with 4 updates ([#1323](https://redirect.github.com/buildpacks/lifecycle/issues/1323)) #### Bugfixes - Buildpack API 0.11 is supported as of lifecycle 0.19.x ([#1326](https://redirect.github.com/buildpacks/lifecycle/issues/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](https://redirect.github.com/buildpacks/lifecycle/issues/1325)) - Log level and color level are configurable via the environment ([#1314](https://redirect.github.com/buildpacks/lifecycle/issues/1314)) - Updates README for 0.19.x ([#1313](https://redirect.github.com/buildpacks/lifecycle/issues/1313)) **Full Changelog**: https://github.com/buildpacks/lifecycle/compare/v0.19.0...release/0.19.1 ### [`v0.19.0`](https://redirect.github.com/buildpacks/lifecycle/releases/tag/v0.19.0): lifecycle v0.19.0 [Compare Source](https://redirect.github.com/buildpacks/lifecycle/compare/v0.18.5...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](https://redirect.github.com/buildpacks/spec/blob/main/platform.md#build-image). The build image can then be orchestrated by a platform implementation such as the [pack CLI](https://redirect.github.com/buildpack/pack) or [tekton](https://redirect.github.com/tektoncd/catalog/tree/main/task/buildpacks). #### 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](https://redirect.github.com/buildpacks/lifecycle/issues/1247) by [@kritkasahni-google](https://redirect.github.com/kritkasahni-google)) - When using Platform API 0.13 or greater, image extensions are no longer experimental ([#1295](https://redirect.github.com/buildpacks/lifecycle/issues/1295) by [@prashantrewar](https://redirect.github.com/prashantrewar)) - When using Platform API 0.13 or greater, image extensions may write into a shared or specific context directory ([#1276](https://redirect.github.com/buildpacks/lifecycle/issues/1276) by [@modulo11](https://redirect.github.com/modulo11)) - Adds support for `ppc64le` architecture ([#1303](https://redirect.github.com/buildpacks/lifecycle/issues/1303) by [@matzew](https://redirect.github.com/matzew)) - Documents `-image` is a deprecated flag ([#1304](https://redirect.github.com/buildpacks/lifecycle/issues/1304) by [@ryanbrainard](https://redirect.github.com/ryanbrainard)) - Bumps dependencies ([#1226](https://redirect.github.com/buildpacks/lifecycle/issues/1226), [#1234](https://redirect.github.com/buildpacks/lifecycle/issues/1234), [#1238](https://redirect.github.com/buildpacks/lifecycle/issues/1238), [#1259](https://redirect.github.com/buildpacks/lifecycle/issues/1259), [#1265](https://redirect.github.com/buildpacks/lifecycle/issues/1265), [#1277](https://redirect.github.com/buildpacks/lifecycle/issues/1277), [#1279](https://redirect.github.com/buildpacks/lifecycle/issues/1279), [#1280](https://redirect.github.com/buildpacks/lifecycle/issues/1280), [#1283](https://redirect.github.com/buildpacks/lifecycle/issues/1283), [#1281](https://redirect.github.com/buildpacks/lifecycle/issues/1281), [#1292](https://redirect.github.com/buildpacks/lifecycle/issues/1292), [#1296](https://redirect.github.com/buildpacks/lifecycle/issues/1296), [#1310](https://redirect.github.com/buildpacks/lifecycle/issues/1310)) - Adds debug statements to the `extender` ([#1298](https://redirect.github.com/buildpacks/lifecycle/issues/1298) by [@natalieparellano](https://redirect.github.com/natalieparellano)) - Updates go to version 1.21.8 #### Bugfixes - The `lifecycle` will always set CNB_TARGET_\* variables during detect, build, and generate ([#1309](https://redirect.github.com/buildpacks/lifecycle/issues/1309) by [@natalieparellano](https://redirect.github.com/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](https://redirect.github.com/buildpacks/lifecycle/issues/1305) by [@ryanbrainard](https://redirect.github.com/ryanbrainard)) - The `creator` errors if the detected group (instead of the order) contains extensions ([#1246](https://redirect.github.com/buildpacks/lifecycle/issues/1246) by [@natalieparellano](https://redirect.github.com/natalieparellano)) - The `exporter` zeroes timestamps when adding extension layers to the app image ([#1289](https://redirect.github.com/buildpacks/lifecycle/issues/1289) by [@natalieparellano](https://redirect.github.com/natalieparellano)) - The `extender` will successfully copy extended run image layers even if the original run image has a duplicated top layer ([#1306](https://redirect.github.com/buildpacks/lifecycle/issues/1306) by [@natalieparellano](https://redirect.github.com/natalieparellano)) #### Library Changes - Consolidates methods that read and write platform spec'd TOML ([#1236](https://redirect.github.com/buildpacks/lifecycle/issues/1236) by [@natalieparellano](https://redirect.github.com/natalieparellano)) **Full Changelog**: https://github.com/buildpacks/lifecycle/compare/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](https://redirect.github.com/c0d1ngm0nk3y), [@jabrown85](https://redirect.github.com/jabrown85), [@kritkasahni-google](https://redirect.github.com/kritkasahni-google), [@loewenstein](https://redirect.github.com/loewenstein), [@matzew](https://redirect.github.com/matzew), [@modulo11](https://redirect.github.com/modulo11), [@natalieparellano](https://redirect.github.com/natalieparellano), [@pbusko](https://redirect.github.com/pbusko), [@phil9909](https://redirect.github.com/phil9909), [@prashantrewar](https://redirect.github.com/prashantrewar), [@ryanbrainard](https://redirect.github.com/ryanbrainard)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.