fix(ci): avoid missing pnpm cache in release jobs#153
Merged
Conversation
ZR233
marked this pull request as ready for review
July 17, 2026 01:27
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.
Summary
actions/setup-nodestep in the Release workflowRoot cause
The release-plz steps completed successfully, but both jobs failed during
Post Setup Node.js. The workflow configured pnpm caching without running pnpm in release-PR-only executions, so the expected store directory did not exist andsetup-nodefailed while saving the cache.Impact
Release and release-PR jobs no longer fail during post-job cleanup when no pnpm store was created.
Validation
git diff --checkactionlintwas not available in the local environment.