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.

Sign up for GitHub

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

Jump to bottom

Preparing jib-core CHANGELOG for 0.22.0 release #3747

Merged
merged 4 commits into from Aug 29, 2022
Merged

Preparing jib-core CHANGELOG for 0.22.0 release #3747

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
34381e1
Preparing jib-core CHANGELOG for 0.22.0 release
mpeddada1 Aug 29, 2022
d4dbaa6
add contributions to CHANGELOG
mpeddada1 Aug 29, 2022
4389f77
Update CHANGELOG.md
mpeddada1 Aug 29, 2022
cb2de9f
Update CHANGELOG.md
mpeddada1 Aug 29, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 6 additions & 0 deletions jib-core/CHANGELOG.md
View file
Open in desktop
Expand Up @@ -4,8 +4,14 @@ All notable changes to this project will be documented in this file.
## [unreleased]

### Added
- Better error messaging when environment map in `container.environment` contains null values ([#3672](https://github.com/GoogleContainerTools/jib/pull/3672)).
- DockerClient interface which is used to make calls to the Docker daemon. This allows for custom implementations to be introduced via SPI ([#3703](https://github.com/GoogleContainerTools/jib/pull/3703)).
- Support for OCI image index manifests ([#3715](https://github.com/GoogleContainerTools/jib/pull/3715)).
- Support for base image layer compressed with zstd ([#3717](https://github.com/GoogleContainerTools/jib/pull/3717)).

### Changed
- Jib now throws an exception when the base image doesn't support target platforms during multi-platform build ([#3707](https://github.com/GoogleContainerTools/jib/pull/3707)).
- Jib now only checks for file existance instead of running the executable passed into `dockerClient.executable` for the purpose of verifying if docker is installed correctly. Users are responsible for ensuring that the docker executable specified through this property is valid and has the correct permissions ([#3742](https://github.com/GoogleContainerTools/jib/pull/3742)).
mpeddada1 marked this conversation as resolved.
Show resolved Hide resolved

### Fixed

Expand Down