fix(ci): Buildx setup so the release Docker job can export gha cache#24
Merged
Conversation
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.
Hotfix for the failed v0.9.0 release run.
publish-dockerfailed withCache export is not supported for the docker driver: the 0.9.0 cycle addedcache-from/cache-to: type=ghato the build-push step without adocker/setup-buildx-actionstep, so the defaultdockerdriver can't export the GHA cache. Addsdocker/setup-buildx-action@v3(creates adocker-containerdriver) before login.Note: the
publish-npmfailure in the same run is a separate, credential-side issue (E404 on PUT to an existing public package = invalid/expiredNPM_TOKEN), not addressed by this code change.