Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update module github.com/buildpacks/lifecycle to v0.20.4 #4831

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 17, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/buildpacks/lifecycle v0.18.5 -> v0.20.4 age adoption passing confidence

Release Notes

buildpacks/lifecycle (github.com/buildpacks/lifecycle)

v0.20.4: lifecycle v0.20.4

Compare Source

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

Chores

Full Changelog: buildpacks/lifecycle@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

v0.20.3: lifecycle v0.20.3

Compare Source

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: buildpacks/lifecycle@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

v0.20.2: lifecycle v0.20.2

Compare Source

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

Full Changelog: buildpacks/lifecycle@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

Compare Source

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

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: buildpacks/lifecycle@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

v0.20.0: lifecycle v0.20.0

Compare Source

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: buildpacks/lifecycle@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

v0.19.7: lifecycle v0.19.7

Compare Source

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

Bugfixes

Full Changelog: buildpacks/lifecycle@v0.19.6...release/0.19.7

v0.19.6: lifecycle v0.19.6

Compare Source

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

Full Changelog: buildpacks/lifecycle@v0.19.5...release/0.19.6

v0.19.5: lifecycle v0.19.5

Compare Source

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

Full Changelog: buildpacks/lifecycle@v0.19.4...release/0.19.5

v0.19.4: lifecycle v0.19.4

Compare Source

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

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: buildpacks/lifecycle@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

v0.19.3: lifecycle v0.19.3

Compare Source

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

Chores

Full Changelog: buildpacks/lifecycle@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

v0.19.2: lifecycle v0.19.2

Compare Source

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: buildpacks/lifecycle@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

v0.19.1: lifecycle v0.19.1

Compare Source

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: buildpacks/lifecycle@v0.19.0...release/0.19.1

v0.19.0: lifecycle v0.19.0

Compare Source

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

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

Full Changelog: buildpacks/lifecycle@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


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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner February 17, 2024 15:31
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch 11 times, most recently from a930943 to 5834687 Compare February 26, 2024 12:09
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch 4 times, most recently from ebf723a to 1795973 Compare March 5, 2024 14:22
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch 2 times, most recently from df6c244 to d42b62e Compare March 7, 2024 20:14
@renovate renovate bot changed the title fix(deps): update module github.com/buildpacks/lifecycle to v0.18.5 fix(deps): update module github.com/buildpacks/lifecycle to v0.19.0 Mar 7, 2024
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch 7 times, most recently from a8e6664 to c750fed Compare March 15, 2024 09:47
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch 4 times, most recently from 821303e to 67aebb4 Compare March 25, 2024 09:46
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch 8 times, most recently from 346412c to 09a97ba Compare October 30, 2024 11:04
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch 6 times, most recently from e55c011 to 4ab65c6 Compare November 8, 2024 08:45
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch 2 times, most recently from 8637aaa to feb6fc8 Compare November 12, 2024 19:57
@renovate renovate bot changed the title fix(deps): update module github.com/buildpacks/lifecycle to v0.20.3 fix(deps): update module github.com/buildpacks/lifecycle to v0.20.4 Nov 12, 2024
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch 4 times, most recently from 11b1b1f to 0114491 Compare November 22, 2024 13:12
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch 6 times, most recently from 5a4a5f4 to a279357 Compare November 27, 2024 14:58
@renovate renovate bot force-pushed the renovate/github.com-buildpacks-lifecycle-0.x branch from a279357 to c62d048 Compare November 28, 2024 09:42
Copy link

sonarcloud bot commented Nov 28, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants