Update google/go-containerregistry #84
Closed
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
This pulls in the estargz support in google/go-containerregistry, which enables buildpack builders to produce estargz layers by simply setting `GGCR_EXPERIMENT_ESTARGZ=1`. Related: opencontainers/image-spec#815 Signed-off-by: Matt Moore <mattmoor@vmware.com>
mattmoor
force-pushed
the
update-ggcr
branch
from
b230287
to
7c9ee0f
Compare
|
Talked to @ekcasey in slack, I am going to try and get a GGCR release cut, and let dependabot do its magic. |
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 pulls in the estargz support in google/go-containerregistry, which enables buildpack builders to produce estargz layers by simply setting
GGCR_EXPERIMENT_ESTARGZ=1.Related: opencontainers/image-spec#815