fix(ci): pin pullable Linux image manifest - #26
Merged
Conversation
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The initial v1.1.0 pin used the immutable multi-platform OCI index digest.
GitHub-hosted job-container initialization returned
manifest unknownfor thattag-plus-index coordinate even though direct registry inspection and local
pulls resolve it.
This follow-up pins the concrete immutable Linux/amd64 image manifest used by
the validation and release jobs:
sha256:ab467b9573f7727a6ded9e6e0518fa87af68c340f73f03be41c192a98a34a633Validation:
docker pullof the published v1.1.0 imagedocker buildx imagetools inspectplatform verificationactionlintgit diff --check