Upgrade pixi.lock to v7; pin CI pixi to v0.79.0 - #84
Merged
Conversation
Beamline pixi installs are moving to lockfile v7, and modern pixi warns on every command while the lock stays v6. Regenerated with pixi 0.79.0 and bumped the CI/pixi-update pins from v0.71.3 in the same change so CI parses the new format. Full test suite green locally under the regenerated lock (101 passed).
Copilot started reviewing on behalf of
Anthony Sligar (sligara7)
September 4, 2026 15:02
View session
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The Pixi version pin updates are consistent across the affected workflows and align with the lockfile’s v7 format.
Pull request overview
Updates the repository’s Pixi tooling to support the newer lockfile format and keep CI aligned with the regenerated lockfile.
Changes:
- Regenerates
pixi.lockin lockfile format v7 (produced by pixi 0.79.0). - Pins GitHub Actions CI to pixi
v0.79.0so the runner can parse and use the v7 lockfile. - Pins the scheduled
pixi updateworkflow to pixiv0.79.0to keep future lock updates consistent.
File summaries
| File | Description |
|---|---|
| pixi.lock | Lockfile updated to format v7 (compatible with pixi 0.79.0). |
| .github/workflows/ci.yml | Pins pixi to v0.79.0 across lint/type-check/tests so CI matches the v7 lockfile format. |
| .github/workflows/pixi-update.yml | Pins pixi to v0.79.0 for automated lockfile refresh PRs. |
Review details
- Files reviewed: 2/3 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Jakub Wlodek (jwlodek)
approved these changes
Sep 4, 2026
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
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.
Beamline pixi installs are moving to lockfile v7, and any modern pixi warns on every command while the lock stays v6.
pixi.lockregenerated with pixi 0.79.0 (format v7)v0.71.3->v0.79.0in the same change so CI parses the new formatFull test suite green locally under the regenerated lock (101 passed, pixi 0.79.0, dev env).