Skip to content

fix(ci): specify pnpm version in action-setup to fix workflow failures#20

Merged
yahyafakhroji merged 1 commit into
mainfrom
claude/fix-pnpm-version-8Flyy
Mar 13, 2026
Merged

fix(ci): specify pnpm version in action-setup to fix workflow failures#20
yahyafakhroji merged 1 commit into
mainfrom
claude/fix-pnpm-version-8Flyy

Conversation

@yahyafakhroji

Copy link
Copy Markdown
Contributor

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.

@yahyafakhroji yahyafakhroji added the release:minor Bump minor version on publish label Mar 13, 2026
@cla-assistant

cla-assistant Bot commented Mar 13, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@yahyafakhroji yahyafakhroji force-pushed the claude/fix-pnpm-version-8Flyy branch 2 times, most recently from 5fe8f08 to 6d25e56 Compare March 13, 2026 15:42
…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.
@yahyafakhroji yahyafakhroji force-pushed the claude/fix-pnpm-version-8Flyy branch from 6d25e56 to b22f3cf Compare March 13, 2026 15:46
@yahyafakhroji yahyafakhroji requested a review from a team March 13, 2026 15:47
@yahyafakhroji yahyafakhroji merged commit daaa2c0 into main Mar 13, 2026
7 checks passed
@yahyafakhroji yahyafakhroji deleted the claude/fix-pnpm-version-8Flyy branch March 13, 2026 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release:minor Bump minor version on publish

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants