fix(scripts): pin pixi to v0.73.0 in provisioning and docs (NEH-170) - #290
Merged
Conversation
The committed pixi.lock is lock-file format v7 (re-locked with pixi 0.73); an unpinned `curl | bash` install gives every unit whatever pixi is latest that day, and an older one cannot read the lock at all — this is exactly what broke the first Rionegro update attempt on 2026-08-03 (pixi 0.63.2 against the v7 lock). setup.sh now installs the pinned version itself when pixi is missing, and warns with the exact self-update command when a different version is present. The PIXI_VERSION variable sits on bash's side of the pipe — the installer reads it; prefixing curl would silently install latest. README.md and README-SETUP.md document the pinned form.
There was a problem hiding this comment.
Pull request overview
Pins pixi v0.73.0 across provisioning and setup documentation to ensure compatibility with the committed v7 lock file.
Changes:
- Automatically installs the pinned pixi version when missing.
- Warns when the installed version differs.
- Updates English and Spanish setup instructions.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
scripts/setup.sh |
Adds pinned installation and version-mismatch guidance. |
README.md |
Documents the pinned installation command. |
README-SETUP.md |
Updates Spanish setup instructions with the pin. |
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.
Pins the pixi installer so provisioning is reproducible and always matches the committed lock format.
Why
pixi.lockis lock-file format v7 (re-locked with pixi 0.73 on 2026-07-24, documented inbackend/DEVELOPMENT.md). The install command in the docs was unpinnedcurl | bash, so every unit got whatever pixi was latest on its provisioning day — and units provisioned before 0.68 can't read v7 at all. This is precisely what broke the first Rionegro update attempt on 2026-08-03: pixi 0.63.2 against the v7 lock (Lock-file version 7 is newer than supported).v0.73.0 is the version the bench unit and Rionegro both run today, field-validated against the committed lock.
Changes
scripts/setup.shdefinesPIXI_VERSION="v0.73.0", installs it itself when pixi is missing (previously it just aborted with an unpinned command to copy-paste), and warns with the exactpixi self-update --versioncommand when a mismatched version is already present. A format mismatch still fails cleanly later atpixi install --locked.curl … | PIXI_VERSION=v0.73.0 bash. The installer readsVERSION="${PIXI_VERSION:-latest}"; writingPIXI_VERSION=… curl … | bashsets the variable for curl only and silently installs latest.README.mdandREADME-SETUP.md(Spanish) document the pinned form.Bumping the pin is now an explicit, reviewed change, to be done together with any lock-format change (the lockstep rule in
backend/DEVELOPMENT.mdalready points here via NEH-170).Linear: NEH-170 (GitHub mirror #221).