fix(ci): specify pnpm version in action-setup to fix workflow failures#20
Merged
Conversation
5fe8f08 to
6d25e56
Compare
…kflow The reusable publish workflow (datum-cloud/actions/publish-npm-package.yaml) reads package.json from the package path (packages/datum-ui), not the repo root. Since that file lacked a packageManager field, pnpm/action-setup@v4 could not determine the pnpm version.
6d25e56 to
b22f3cf
Compare
gaghan430
approved these changes
Mar 13, 2026
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.
pnpm/action-setup@v4 requires an explicit version when it cannot auto-detect from package.json packageManager field. Add version: 10 to all pnpm/action-setup steps across CI, release, and publish workflows.