etherpad 2.5.1 locked to pnpm version 10.18.0

[jkbzh]

Describe the bug
Starting from 2.5.1, etherpad-lite/package.json includes a packageManager field, which locks
pnpm to version 10.18.0:
"packageManager": "pnpm@10.18.0"

However, at least in debian12 / arm64, the default pnpm version that is installed is 10.18.3.
This gives an error when trying to install etherpad 2.5.1 from scratch.

To overcome this issue I had to downgrade pnpm to 10.18.0.

To Reproduce
Steps to reproduce the behavior:

1. Install pnpm 10.18.3 (latest version)
2. Try to install etherpad from scratch following the README procedure for Linux
3. See error

Expected behavior
I would expect that etherpad be locked to 10.18.* so that it can benefit from at least patch upgrades, potentially minor upgrades, which often fix bugs and security issues and are allegedly backwards compatible.

Server (please complete the following information):

• Etherpad version: 2.5.1
• OS: Debian 12.2 / aarch64
• Node.js version (node --version): v22.20.0
• npm version (npm --version): 10.18.3
• Is the server free of plugins: this was for an install from scratch and part of the process included installing the ep_ldapauth plugin. This plugin has no declared dependency with pnpm in its package.json. The pnpm dependency failure didn't let us reach the plugin install stage.

Additional context

I don't know what would be the best solution to make sure the install will work when pnpm has been upgraded to a new minor or patch version. The packageManager syntax doesn't seem to allow for that.

Here's more context from a related issue I found in the pnpm repository:

pnpm/pnpm#8086

[SamTV12345]

Hi @jkbzh thanks for raising the issue. Yes this can be an issue. I am currently working on a tool that includes all major package managers called gnpm. It's pretty much feature complete the only thing that is missing is auto upgrading. It currently only fetches all currently available versions of node and pnpm once. The idea is basically it auto downloads the highest compatible node and pnpm version and runs it when you execute gnpm .
It's a bit of a pitty that you have to install pnpm globally and can't have it on a per project basis. This is what my go cli tool tries to solve.

Other solution would be npm install -g pnpm@10.18.3