ci: drop v0.41.4 pixi-version pin in unittest and package workflows#75
Merged
Conversation
The update-lockfiles workflow regenerates pixi.lock with the latest pixi (currently producing version 7 lockfiles), but the test/package workflows pinned to v0.41.4 only read older lockfile versions. Removing the pin so all workflows use the same default pixi version and stay in sync with the auto-regenerated lockfile. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
pixi-version: v0.41.4pin inunittest.yml(1 occurrence) andpackage.yml(2 occurrences) so they use the default pixi installed byprefix-dev/setup-pixi.Why
update-lockfiles.ymlis unpinned and uses the latest pixi (which now produces lockfile version 7). The pinned test/package workflows on v0.41.4 only read older lockfile versions, so the next auto-regen ofpixi.lockwould break CI. This is the same root cause as the recent timepix_geometry_correction breakage (fixed in that repo's PR #70).Test plan
🤖 Generated with Claude Code