Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lockfile not invalidated when removing platforms #2906

Open
2 tasks done
ruben-arts opened this issue Jan 14, 2025 · 0 comments
Open
2 tasks done

Lockfile not invalidated when removing platforms #2906

ruben-arts opened this issue Jan 14, 2025 · 0 comments
Labels
🐞 bug Something isn't working 🗒️ configuration Issue related to configuration of project or global behavior

Comments

@ruben-arts
Copy link
Contributor

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

When removing the platforms in a manifest, the lockfile is not invalidated

pixi init repro && cd repro
pixi add python # creates lockfile and installs environment
pixi project platform remove YOUR_PLATFORM # Doesn't update lockfile
pixi remove python # Doesn't update lockfile
pixi install # Doesn't update lockfile

Issue description

We should invalidate the lockfile on a mismatch between the platforms.

Expected behavior

The lockfile is in sync with the manifest after a command that modifies content that is related to the lockfile.

@ruben-arts ruben-arts added 🐞 bug Something isn't working 🗒️ configuration Issue related to configuration of project or global behavior labels Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working 🗒️ configuration Issue related to configuration of project or global behavior
Projects
None yet
Development

No branches or pull requests

1 participant