Releases: buildpacks/lifecycle
lifecycle v0.10.2
lifecycle v0.10.2
Welcome to v0.10.2
, a beta release of the Cloud Native Buildpack Lifecycle.
APIs
Platform API
To configure the platform API, set CNB_PLATFORM_API=<api>
in the lifecycle environment.
Buildpack API
Each buildpack may configure the buildpack API by setting the api
key in buildpack.toml
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.
Features
- Updates ggcr to version 0.3.0 (#493)
Bug Fixes
lifecycle v0.10.1
lifecycle v0.10.1
Welcome to v0.10.1
, a beta release of the Cloud Native Buildpack Lifecycle.
APIs
Platform API
To configure the platform API, set CNB_PLATFORM_API=<api>
in the lifecycle environment.
Buildpack API
Each buildpack may configure the buildpack API by setting the api
key in buildpack.toml
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.
Bug Fixes
launcher
continues to process layer env modifications from subsequent buildpacks after encountering a buildpack that has no layers directory (#492)
lifecycle v0.10.0
lifecycle v0.10.0
Welcome to v0.10.0
, a beta release of the Cloud Native Buildpack Lifecycle.
APIs
Platform API
To configure the platform API, set CNB_PLATFORM_API=<api>
in the lifecycle environment.
Buildpack API
Each buildpack may configure the buildpack API by setting the api
key in buildpack.toml
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.
Features
- When using buildpack API
0.5
or greater, the buildpack plan is read only. BOM entries must be written tolaunch.toml
and unmet requires must be written tobuild.toml
. A build BOM may be written tobuild.toml
, this will be output inreport.toml
(#396, #461) - When using buildpack API
0.5
or greater, the default action for environment variables is override (#394, #483) - When using buildpack API
0.5
or greater, buildpacks may contribute an exec.d executable to the app image (#398, #473) - When using platform API
0.5
or greater, all default file paths that were previously relative to the working directory are relative to the layers directory (#393, #454) builder
adds the buildpack homepage toio.buildpacks.build.metadata
label (#349, #418)exporter
falls back to slow behavior if writing to daemon fails with performance optimization (#487)rebaser
validates mixins (#425, #450)rebaser
updatesio.buildpacks.stack.*
labels from run image (#390, #407)
Bug Fixes
lifecycle v0.9.3
lifecycle v0.9.3
Welcome to v0.9.3
, a beta release of the Cloud Native Buildpack 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.
Bug Fixes
lifecycle v0.9.2
lifecycle v0.9.2
Welcome to v0.9.2
, a beta release of the Cloud Native Buildpack 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.
Bug Fixes
- Removes all unsafe usage of
filepath.Glob
(#412, #432). - Support Artifact Registry (#416, #417)
- Environment variables set by windows profile scripts are now set in the process environment (#359, #399)
- Graceful handling of empty cached layers (#386, #397)
-no-color
flag strips color from buildpack logs (#329, #434)- Fixes missing error checks (#433)
- Bash processes properly handle more than nine args correctly(#445, #446)
lifecycle v0.9.1
lifecycle v0.9.1
Welcome to v0.9.1
, a patch release of the Cloud Native Buildpack Lifecycle.
Prerequisites
The lifecycle runs as a normal user in a series of unprivileged Linux 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.
Bug Fixes
lifecycle v0.9.0
lifecycle v0.9.0
Welcome to v0.9.0
, a minor release of the Cloud Native Buildpack Lifecycle.
APIs
Platform API
To configure the platform API, set CNB_PLATFORM_API=<api>
in the lifecycle environment.
Buildpack API
Each buildpack may configure the buildpack API by setting the api
key in buildpack.toml
Prerequisites
The lifecycle runs as a normal user in a series of unprivileged Linux 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.
Features
- The lifecycle now provides support for multiple platform and buildpack APIs (#344, #347 #365, RFC-0041, RFC-0049).
CNB_BUILDPACK_DIR
provides the buildpack directory in the buildpack environment (#325, #320, RFC-0036).- Buildpacks may contribute process-type-specific profile scripts and environment variables (#322, #327, RFC-0042).
- Lifecycle returns more informative error codes to the platform (#306, #346, #350, buildpacks/spec#115).
- Buildpacks may add labels to the app image (#321, #353, RFC-0034).
exporter
,rebaser
, andcreator
write a report file containing the identifier of the new app image (#333, #352, #364, RFC-0040, buildpacks/spec#123).- When using Platform API
0.4
, users may supply additional arguments to buildpack-provided process types (#356, #370, RFC-0045). - When using buildpack API
0.4
, shell commands can be built from arguments, allowing for easy consumption of additional user-provided arguments (#354, #358, RFC-0045). - Introductory support for windows containers (#238, #237, #326).
Bug Fixes
- Lifecycle properly sets GID of app image files during export (#362).
- Rebase preserves image OS and architecture (#371).
Deprecations
- When using buildpack API
0.3
or greater,requires.version
andrequires.or.version
have been deprecated in the Build Plan (#330, #369, RFC-0043).
Removals
- When using platform API
0.4
,version
has been removed from build plan entries in the Bill-of-Materials. If a buildpack returns an entry withversion
it will be relocated tometadata.version
in the BOM (#357, #367, buildpacks/spec#117). - When using platform API
0.4
,CNB_PROCESS_TYPE
will not be respected at launch. Instead, set theENTRYPOINT
to a process type (RFC-0049).
Known Issues
- On windows:
- When using platform API
0.4
windows run images must havePATH
set inEnv
in the image config. - Environment variables set by profile scripts will not be available to the command, although they will be available to any children of the command. (#359).
- Launched processes may not receive signals in some scenarios (#360).
- Configuring exact security IDs on the stack is not supported (#343).
- When using platform API
lifecycle v0.8.1
lifecycle v0.8.1
Welcome to v0.8.1
, a patch release of the Cloud Native Buildpack Lifecycle.
Prerequisites
The lifecycle runs as a normal user in a series of unprivileged Linux 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.
Bug Fixes
lifecycle v0.8.0
lifecycle v0.8.0
Welcome to v0.8.0, a beta release of the Cloud Native Buildpack Lifecycle. This release introduces performance improvements, style improvements, and bug fixes.
Prerequisites
The lifecycle runs as a normal user in a series of unprivileged Linux 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.
Features
Performance Improvements
Bug Fixes
lifecycle v0.7.5
lifecycle v0.7.5
Welcome to v0.7.5
, a patch release of the Cloud Native Buildpack Lifecycle.
Prerequisites
The lifecycle runs as a normal user in a series of unprivileged Linux 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.