Skip to content

chore: align devEngines pnpm version with packageManager - #1467

Open
l2ysho wants to merge 10 commits into
masterfrom
claude/pnpm-infinite-loop-ecd46b
Open

l2ysho wants to merge 10 commits into
masterfrom
claude/pnpm-infinite-loop-ecd46b

Conversation

@l2ysho

@l2ysho l2ysho commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Note

TL;DR: devEngines.packageManager still pinned pnpm 11.11.0 while packageManager says 12.6.0. This aligns it to 12.6.0 and bumps apify/actions/pnpm-install to v1.6.2 so Windows CI can run pnpm 12.

Follow-up: Renovate should bump all three pnpm pins together.

🤖 Generated with Claude Code

#1414 bumped packageManager and volta.pnpm to 12.4.1 but left
devEngines.packageManager and the lockfile's packageManagerDependencies
at 11.11.0, so every pnpm command warns about the mismatch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@l2ysho l2ysho added adhoc Ad-hoc unplanned task added during the sprint. t-builders Issues owned by the Builders team. labels Sep 29, 2026
@l2ysho
l2ysho marked this pull request as ready for review September 29, 2026 09:15
@l2ysho
l2ysho requested a review from DaveHanns as a code owner September 29, 2026 09:15
apify/actions/pnpm-install pins pnpm/action-setup@v6.0.8, which cannot
run pnpm 12 on Windows runners. Use a local copy of that action with
v6.1.0 until apify/actions ships the bump.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@l2ysho l2ysho changed the title chore: align devEngines pnpm version with packageManager chore: move CI to pnpm 12 and align devEngines Sep 29, 2026
The bump belongs in apify/actions instead of a local copy.

This reverts commit 99091f4.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@l2ysho l2ysho changed the title chore: move CI to pnpm 12 and align devEngines chore: align devEngines pnpm version with packageManager Sep 29, 2026
l2ysho added a commit to apify/actions that referenced this pull request Sep 30, 2026
…rt (#48)

> [!NOTE]
> **TL;DR:** `pnpm-install` pins `pnpm/action-setup@v6.0.8`, which
cannot run pnpm 12 on Windows. Bump to v6.1.0, which adds pnpm 12
support.

- With `devEngines.packageManager` set to pnpm 12.4.1, every Windows job
fails at the first `pnpm run` in pwsh: the pnpm shim is `not recognized
as an internal or external command`. [Failing
job](https://github.com/apify/apify-cli/actions/runs/36547790795/job/109338592927)
from apify/apify-cli#1467.
- [pnpm/action-setup
v6.1.0](https://github.com/pnpm/action-setup/releases/tag/v6.1.0)
contains only pnpm/action-setup#288, "support pnpm v12".
- apify/apify-cli#1467 waits for a release with this change.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
l2ysho and others added 7 commits September 30, 2026 22:59
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e-loop-ecd46b

# Conflicts:
#	.github/workflows/check.yaml
#	.github/workflows/docs.yaml
#	.github/workflows/e2e.yaml
#	.github/workflows/pre_release.yaml
#	.github/workflows/publish_to_npm.yaml
#	.github/workflows/release.yaml
#	.github/workflows/version_docs.yaml
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-builders Issues owned by the Builders team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants