Skip to content

chore: upgrade pixi.lock to v7 format - #23

Open
Padraic Shafer (padraic-shafer) wants to merge 2 commits into
mainfrom
upgrade-pixi-lock-v7-pc-1783433073-20656
Open

chore: upgrade pixi.lock to v7 format#23
Padraic Shafer (padraic-shafer) wants to merge 2 commits into
mainfrom
upgrade-pixi-lock-v7-pc-1783433073-20656

Conversation

@padraic-shafer

Copy link
Copy Markdown

Why this re-lock was performed

pixi lock file format v6 is superseded by v7 (pixi ≥ 0.47 writes v7 by default).
Migrating keeps pixi lock --check in CI and modern pixi installs consistent with
the committed lock file.

The lock was re-run using the existing pixi.toml manifest constraints —
no dependency specifications were changed.

Verification

  • Lock file format: v6 → v7 ✅
  • pixi lock --check passes after upgrade ✅

Lock file details

pixi.lock

  • Format: v6 → v7
  • Solve method: --no-install
  • pixi lock --check: PASS
  • No package versions changed — format-only migration (610 packages).

Upgrade all pixi.lock files in this repository from lock file format
v6 to v7. The lock was re-run using existing manifest constraints.

See PR description for details on package version changes (if any).
@padraic-shafer

Copy link
Copy Markdown
Author

This PR should be merged only after the pixi binary is updated on the affected hosts. Otherwise the pixi run commands will fail when the lock file uses a newer version than the binary expects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants