sync-version job fails while installing MCP dependencies with pnpm 11

[timelis]

Description

The sync-version job in the Dokploy Docker Build workflow is not completing. It fails in the first step, Sync version to MCP repository, so the generated MCP tools and package version are not synchronized with Dokploy releases. Because the MCP, CLI, and SDK sync steps run sequentially, the later sync steps are also skipped after this failure.

The workflow currently installs pnpm without a version constraint:

npm install -g pnpm
pnpm install

This now installs pnpm v11, and the MCP dependency installation exits with:

ERR_PNPM_IGNORED_BUILDS Ignored build scripts: esbuild@0.27.7

The MCP repository is consequently still at package version 0.29.3, despite newer Dokploy releases.

Evidence

The same failure is visible in multiple release runs:

• https://github.com/Dokploy/dokploy/actions/runs/26316640252/job/77477970237
• https://github.com/Dokploy/dokploy/actions/runs/29243275905/job/86795720278

Affected workflow:

• https://github.com/Dokploy/dokploy/blob/main/.github/workflows/dokploy.yml

Expected behavior

The sync-version job should install the MCP dependencies, regenerate the OpenAPI-derived tools, update the package version, and push the generated changes after each main release.

Related issue

Dokploy/mcp#59 reports the same pnpm v11 / esbuild installation failure in the MCP Docker build path:

• Docker compose build fails: lockfile excluded and pnpm latest breaks install mcp#59

Possible direction

Pinning pnpm to a compatible v10 release such as 10.33.0 appears to be one possible fix. Before implementing it, it would be useful to verify whether the repository can instead declare and enforce its package-manager version through Corepack/packageManager, or whether pnpm's build-script approval configuration can make the workflow compatible with v11 without an unnecessarily narrow version pin.

[dosubot]

Hi @timelis! I'm Dosu and I'm helping the Dokploy team.

Your analysis is correct. The sync-version job in .github/workflows/dokploy.yml uses bare npm install -g pnpm without a version constraint in three places (for MCP, CLI, and SDK sync steps) . This is what's pulling in pnpm v11 and triggering the ERR_PNPM_IGNORED_BUILDS failure.

Interestingly, the main Dokploy repository already declares "packageManager": "pnpm@10.22.0" in its package.json files [2], but the workflow ignores this and installs pnpm globally instead. The simplest fix options would be:

1. Pin the version in the workflow — change npm install -g pnpm to npm install -g pnpm@10.22.0 (or a 10.x range) in the sync-version job steps.
2. Use Corepack — enable Corepack in the workflow so it respects the packageManager field from whichever repository is being operated on (the MCP repo would also need its own packageManager field).
3. Configure pnpm v11 compatibility — add pnpm.onlyBuiltDependencies to the MCP's package.json to allowlist esbuild, which is how pnpm v11 expects build scripts to be approved.

Option 1 is the lowest-friction fix since it only touches the workflow file and matches what the repository already declares. Option 3 would be the forward-looking approach if the goal is to eventually adopt pnpm v11 across the ecosystem.

There's no existing PR addressing this specific issue in the workflow.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[timelis]

I'm currently working on this issue, and I'll submit a pull request once I find a good solution.

[Siumauricio]

Fixed in b6190ff ("fix(ci): pin pnpm and strip v prefix in sync-version job"): the sync-version job now pins pnpm to a version compatible with the MCP repo's configuration instead of installing latest, so the ERR_PNPM_IGNORED_BUILDS failure for esbuild no longer occurs. The Dokploy-to-MCP version and generated tool sync is working again, and new MCP releases are building normally.