ci: drop pnpm cache from release workflow#6
Merged
mergify[bot] merged 1 commit intoMay 26, 2026
Conversation
`actions/setup-node` with `cache: pnpm` requires a `pnpm-lock.yaml` to
compute the cache key, but this package has no dependencies and ships
no lockfile — so the step failed ("Dependencies lock file is not
found") before reaching `pnpm publish`, which is why the 0.1.0 release
run never published to npm.
The workflow only runs `pnpm publish` (no install), so there's nothing
to cache. Remove the cache option.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 ApprovalWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 ReviewsWonderful, this rule succeeded.
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
kozlek
approved these changes
May 26, 2026
There was a problem hiding this comment.
Pull request overview
Fixes the npm release workflow failure by removing actions/setup-node’s pnpm cache configuration, which currently hard-fails because the repo has no pnpm-lock.yaml and the workflow doesn’t run pnpm install anyway.
Changes:
- Remove
cache: pnpmfrom the release workflow’sactions/setup-nodestep to prevent cache-key computation failures when no lockfile exists.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
remyduthu
approved these changes
May 26, 2026
Merge Queue Status
This pull request spent 19 seconds in the queue, including 4 seconds running CI. Required conditions to merge
|
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
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
The
Publish to npmrelease workflow failed on the0.1.0release (run) at theactions/setup-nodestep:cache: pnpmrequires apnpm-lock.yamlto compute the cache key, but this package has no dependencies and no lockfile (it only ships SVGs). The step fails before reachingpnpm publish, so the release never published to npm — this is why the OIDC release path had never actually worked (it had never been exercised until 0.1.0).The workflow only runs
pnpm publish(nopnpm install), so there's nothing to cache. This drops thecache: pnpmoption.After merge
Re-cut the
0.1.0release from the fixedmain(the existing0.1.0tag points at the pre-fix commit, andreleaseevents run the workflow from the tag's commit — so it must be recreated after this lands). npm is still at0.0.0, so reusing0.1.0is safe.🤖 Generated with Claude Code