Skip to content

Migrate build from pnpm 8 (EOL) to pnpm 10 or 11 #313

@qweered

Description

@qweered

Summary

package.json pins "packageManager": "pnpm@8.5.0", and pnpm-lock.yaml is still lockfileVersion: '6.0'. pnpm 8 has reached end-of-life, so distributions and downstream packagers that build the @caddyserver/caddyfile-language-server workspace from source are being pushed to drop pnpm 8 from their toolchains.

Why this matters

Newer pnpm (10/11) refuses to use the lockfileVersion: '6.0' lockfile (it's ignored as incompatible), so a frozen-lockfile install fails outright. Anyone building from source with a current pnpm therefore can't do so without first regenerating the lockfile — which is exactly the situation in nixpkgs, where caddyfile-language-server is one of the last consumers keeping the EOL pnpm_8 package alive.

Suggested change

  • Bump packageManager to pnpm@10 or pnpm@11.
  • Regenerate pnpm-lock.yaml with the new pnpm (pnpm install --lockfile-only), which upgrades it to lockfileVersion: '9.0'.
  • Verify CI / the pnpm --filter=@caddyserver/caddyfile-language-server run build workflow still passes.

This keeps the project on a supported pnpm and unblocks source-based packagers. Happy to open a PR if that's helpful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions