fix: respect frozen/locked inputs for pixi list

[wpbonelli]

This action runs the following sequnce

1. pixi install ...
2. pixi info ...
3. pixi list ...

Running pixi list without --frozen or --locked will try to update dependencies and lockfile. I think these options need to be passed through to pixi list to keep the environment established by a locked or frozen install from changing.

[pavelzw]

pixi list updating your lockfile shouldn't happen when running with the default settings of setup-pixi, right? Then, by default you are using pixi install --locked and if the lockfile differs, it should crash even before pixi list would be run?

But I can see this being relevant for --frozen (and in general for soundness).

We should add a deprecation warning for pixi<0.14.0 like here:

setup-pixi/src/main.ts

Line 85 in 92e1dd3

'pixi list is not supported for pixi versions < `v0.13.0`. Please set `pixi-version` to `v0.13.0` or later.'

[pavelzw]

oops misclicked

[wpbonelli]

pixi list updating your lockfile shouldn't happen when running with the default settings of setup-pixi, right? Then, by default you are using pixi install --locked and if the lockfile differs, it should crash even before pixi list would be run?

But I can see this being relevant for --frozen (and in general for soundness).

Yes --frozen is where I saw this MODFLOW-USGS/modflow6#1713 (comment).

I understand the difference between that and --locked now.

[pavelzw]

Lgtm
The linter (pnpm lint) is still failing. Can you take care of that?

Also, can you update this test to use 0.14.0?

setup-pixi/.github/workflows/test.yml

Line 184 in 92e1dd3

pixi-url: https://github.com/prefix-dev/pixi/releases/download/v0.13.0/pixi-x86_64-unknown-linux-musl

[pavelzw]

Thanks @wpbonelli! I'll release this fix together with #95 later.