pixi list --locked updates the lockfile

[benmoss]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

pixi init
pixi add --no-lockfile-update crane
pixi list --locked

Issue description

From the description of --locked I would expect it to exit non-zero and not update the lockfile, but instead it updates the lockfile and reports the resolved crane version.

--locked
Check if lockfile is up-to-date before installing the environment, aborts when lockfile isn't up-to-date with the manifest file

Expected behavior

Something like

pixi list --locked
× lock-file not up-to-date with the project