[notme-18450e] fix(ci): pin pnpm version in the publish-dpop workflow#43
Merged
Conversation
The publish run failed at setup: "No pnpm version is specified." pnpm/action-setup infers the version from package.json#packageManager, and this repo's root has no such field, so it must be passed explicitly. ci.yml already does exactly this (version: 10) — the new workflow just didn't copy it. Caught by tagging dpop-v0.1.0, which is the right place to catch it: the run failed before the publish step, so no partial or broken version reached the registry. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
dpop-v0.1.0publish run failed at setup with "No pnpm version is specified."pnpm/action-setupinfers the version frompackage.json#packageManager, and this repo's root has no such field, so it must be passed explicitly.ci.ymlalready does this (version: 10) — the new workflow just didn't copy it.It failed before the publish step, so nothing partial or broken reached the registry. Re-tagging after this merges.
🤖 Generated with Claude Code
https://claude.ai/code/session_01UNahXs8dda3vttpWrVwVaA