work around a bug in pixi that disallows custom PyPI servers#11331
Merged
Conversation
github-actions
Bot
added
the
Automation
Collaborator
Author
|
merging since this appears to work around the issue that is breaking CI in other PRs, if the typing error is real it will need to be fixed in a different PR. |
Contributor
|
Weird! I would have expected the CI run from e670560 : 
|
Contributor
Collaborator
Author
|
let's revert this PR after the fix in pixi has been released |
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 install --lockedfails on every PR because cachedpixi.lockis stale (and onlymainpushes can refresh it) #11330Might require pinning the pixi versions used by
setup-pixi/pixi-lock/cache.