chore(ci): bump pixi-version to v0.70.2 to read lock-format v7#288
Open
mvillmow wants to merge 1 commit into
Open
chore(ci): bump pixi-version to v0.70.2 to read lock-format v7#288mvillmow wants to merge 1 commit into
mvillmow wants to merge 1 commit into
Conversation
Telemachy CI pins setup-pixi to v0.67.2, which can only read pixi lock-format v6 and fails with "Lock-file version 7 is newer than supported; Maximum supported version: 6" on any v7 lock. Open PRs #263/#271/#273/#276 intentionally ship v7 locks (multi-platform macOS/Windows + large mcp/otel dep trees), so their entire pipeline dies at `pixi install`. Bump all 9 pixi-version pins (_required.yml x7, release.yml x2) to v0.70.2, matching sibling repo Agamemnon which already runs v0.70.2 on main with v7 locks. v0.70.2 is backward-compatible: `pixi install --locked` against main's current v6 lock succeeds (warn-only, lock not rewritten), so this does not red main. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: mvillmow <4211002+mvillmow@users.noreply.github.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.
What
Bump
pixi-versionin CI fromv0.67.2tov0.70.2across both workflows:.github/workflows/_required.yml(7 pins).github/workflows/release.yml(2 pins)No other changes.
Why
CI pins setup-pixi to v0.67.2, which can only read pixi lock-format v6. Any v7 lock fails the install step with:
Open PRs #263, #271, #273, #276 intentionally ship v7 pixi.lock files (multi-platform macOS/Windows + large mcp/otel dep trees). With the current pin, their entire pipeline dies at
pixi install— every job reds. This bump unblocks all four.Ecosystem consistency
Sibling repo Agamemnon already runs pixi v0.70.2 on main with v7 locks successfully. This is the consistent fix.
Safety: does not red main
main's own
pixi.lockis still v6. pixi v0.70.2 is backward-compatible. Verified locally with the exact CI command:pixi install --lockedagainst main's v6 lock → exit 0 (warn-only: "older format (v6)"; the lock is not rewritten, stays v6).pixi install --lockedagainst feat: add multi-platform support for macOS and Windows #263's v7 lock → exit 0, no version error.So this change is safe on main and unblocks the v7 PRs.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com