ci: update pixi to v0.73.0 and migrate pixi.lock to lockfile v7 - #51
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pixi.lockis still on lock file formatversion: 6, and every workflow pinspixi-version: v0.62.2.Pixi bumped the lock file format to v7 somewhere between 0.66 and 0.73, and
rattler_lockrefuses to read a lock file newer than the version it supports. That makes the current combination a trap: as soon as anything regenerates the lock with a current pixi, every CI job that reads it fails. The spec repo hit exactly this and fixed it the same way in substrait-io/substrait#1134.This matters now because substrait-io/substrait#1075 switches us to Renovate, which does refresh
pixi.lockfor dependency updates. On the Mend-hosted Renovate App that behaviour is enabled globally by Mend rather than by us, so it can start happening without warning on their schedule. Getting the format migration in first removes that risk.pixi-versionfromv0.62.2tov0.73.0across the 14 references in.github/workflows, matching the version the spec repo pins.pixi.lock, which migrates it toversion: 7.The lock file diff is large but is a pure format migration. Pixi reports
the lock file is up-to-date but uses an older format (v6), re-solving all environments using locked content to upgrade to v7, so the locked content is preserved: all 351 package URLs are byte-identical before and after, with nothing added or removed.