fix(deps): update module github.com/buildpacks/lifecycle to v0.20.1 #4831
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/github.com-buildpacks-lifecycle-0.x
branch
11 times, most recently
from
a930943
to
5834687
Compare
renovate
bot
force-pushed
the
renovate/github.com-buildpacks-lifecycle-0.x
branch
4 times, most recently
from
ebf723a
to
1795973
Compare
renovate
bot
force-pushed
the
renovate/github.com-buildpacks-lifecycle-0.x
branch
2 times, most recently
from
df6c244
to
d42b62e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-buildpacks-lifecycle-0.x
branch
7 times, most recently
from
a8e6664
to
c750fed
Compare
renovate
bot
force-pushed
the
renovate/github.com-buildpacks-lifecycle-0.x
branch
4 times, most recently
from
821303e
to
67aebb4
Compare
renovate
bot
force-pushed
the
renovate/github.com-buildpacks-lifecycle-0.x
branch
6 times, most recently
from
33e67e8
to
3d51652
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-buildpacks-lifecycle-0.x
branch
6 times, most recently
from
c95ff92
to
93ffeab
Compare
renovate
bot
force-pushed
the
renovate/github.com-buildpacks-lifecycle-0.x
branch
7 times, most recently
from
c571a92
to
f2c3f37
Compare
renovate
bot
force-pushed
the
renovate/github.com-buildpacks-lifecycle-0.x
branch
7 times, most recently
from
395b037
to
c89d07a
Compare
renovate
bot
force-pushed
the
renovate/github.com-buildpacks-lifecycle-0.x
branch
from
c89d07a
to
2c8d3f2
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.18.5->v0.20.1Release Notes
buildpacks/lifecycle (github.com/buildpacks/lifecycle)
v0.20.1Compare 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
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.0Compare 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
restorerrestores cached launch layers even if they are not found in the previous image (#1346 by @pbusko)restorerensures read access to the run image selected by extensions (#1364 by @pbusko)Bugfixes
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.7Compare 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.6Compare 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.5Compare 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
detector, when determining if a base image satisfies target constraints declared by a buildpack, also uses information from/etc/os-releasewhen distro information is not present in the run image labels (https://github.com/buildpacks/lifecycle/pull/1352 by @natalieparellano)Full Changelog: buildpacks/lifecycle@v0.19.4...release/0.19.5
v0.19.4: lifecycle v0.19.4Compare 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
/etc/os-releasewhen distro information is not present in the run image labels (#1347 by @pbusko)Library Changes
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.3Compare 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
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.2Compare 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
Chores
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.1Compare 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
Bugfixes
io.buildpacks.base.distro.nameandio.buildpacks.base.distro.version(#1325)Full Changelog: buildpacks/lifecycle@v0.19.0...release/0.19.1
v0.19.0: lifecycle v0.19.0Compare 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
exporteraccepts a-parallelflag to enable exporting the app image and cache image in parallel (#1247 by @kritkasahni-google)ppc64learchitecture (#1303 by @matzew)-imageis a deprecated flag (#1304 by @ryanbrainard)extender(#1298 by @natalieparellano)Bugfixes
lifecyclewill always set CNB_TARGET_* variables during detect, build, and generate (#1309 by @natalieparellano)rebaserwhen-run-imageis not provided will find the run image name inio.buildpacks.lifecycle.metadatainstead of performing a no-op (on Platform API 0.12) (#1305 by @ryanbrainard)creatorerrors if the detected group (instead of the order) contains extensions (#1246 by @natalieparellano)exporterzeroes timestamps when adding extension layers to the app image (#1289 by @natalieparellano)extenderwill 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.
This PR was generated by Mend Renovate. View the repository job log.