Skip to content

fix(ci): drop hardcoded pnpm version, defer to packageManager#12

Merged
JohnMcLear merged 2 commits intomainfrom
fix/pnpm-version-conflict
May 8, 2026
Merged

fix(ci): drop hardcoded pnpm version, defer to packageManager#12
JohnMcLear merged 2 commits intomainfrom
fix/pnpm-version-conflict

Conversation

@JohnMcLear
Copy link
Copy Markdown
Member

Summary

The post-merge release run for #11 failed with:

Error: Multiple versions of pnpm specified:

  • version 10 in the GitHub Action config with the key "version"
  • version pnpm@11.0.6 in the package.json with the key "packageManager"

The publish job runs actions/checkout@v6 for ether/etherpad-lite first (pinned to pnpm@11 via packageManager), then pnpm/action-setup@v6 with version: 10. Action-setup balks at the mismatch.

Drop the hardcoded version: 10 from both workflows so action-setup takes the pnpm version from packageManager (which is the desired source of truth across the rest of the plugin ecosystem). After this lands, the next merge to main will trigger a clean publish of v0.5.x.

Test plan

  • Fix reviewed in workflow YAML.
  • Will be exercised on next merge to main — release job should reach the publish step instead of erroring at Install pnpm.

🤖 Generated with Claude Code

@qodo-code-review
Copy link
Copy Markdown

ⓘ You've reached your Qodo monthly free-tier limit. Reviews pause until next month — upgrade your plan to continue now, or link your paid account if you already have one.

JohnMcLear added 2 commits May 8, 2026 10:54
The publish job checks out etherpad-lite core first (pinned to
pnpm@11 via packageManager); pnpm/action-setup@v6 then errors with
'Multiple versions of pnpm specified' because the workflow's version: 10
clashes with the checked-out repo's packageManager.

Removing 'version:' lets action-setup take pnpm@11 from packageManager,
which is what we actually want for compatibility with the rest of the
plugin ecosystem and what the test job already does.
action-setup infers the pnpm version from this field. The test job
doesn't check out an upstream repo, so without it action-setup errors
'No pnpm version is specified'.
@JohnMcLear JohnMcLear force-pushed the fix/pnpm-version-conflict branch from 739225c to 6a6fc11 Compare May 8, 2026 09:55
@JohnMcLear JohnMcLear merged commit d40113b into main May 8, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant