MAINT: Set Pixi relative exclude-newer#2572
Merged
VeckoTheGecko merged 1 commit intoParcels-code:mainfrom Apr 9, 2026
Merged
Conversation
VeckoTheGecko
force-pushed
the
exclude-newer
branch
from
2a9e804 to
2e9ac14
Compare
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.
mainfor normal development,v3-supportfor v3 support)As of yesterday, https://github.com/prefix-dev/pixi/releases/tag/v0.67.0 now has support for relative exclude newer. E.g.,
will exclude all packages that have been released within the last 5 days. This better safeguards us against packages being compromised and posting malicious code (these packages are often taken down within a few days). This is particularly useful since we don't commit a lockfile. We often don't work right at the bleeding edge - requiring 'just-released' features - so this wont affect us noticeably.
In security lingo this is known as a "dependency cooldown" (blog: We should all be using dependency cooldowns). Many packages are adopting this. We have already adopted it for our GitHub Actions.
Note that this would need to be revisited if we decide to add a nightly testing environment in future. See pydata/xarray#11269 (comment) for more discussion on that topic.