[pavelzw]

Description

Stacked on #7384.

Fixes #5810.

Adds exclude-newer to the pixi configuration, with the same shape as exclude-newer in a manifest:

# config.toml
exclude-newer = "7d"
# or
exclude-newer = { cutoff = "7d", exemptions = { ruff = "*" } }

As settled in #5810, it is the starting point for new manifests and for pixi exec, and never applies implicitly to an existing workspace, so a lock file doesn't depend on the configuration of whoever runs pixi:

• pixi init writes it into the exclude-newer of the new workspace (pixi.toml, pyproject.toml and from an environment file). The cutoff is written as configured, e.g. 7d.
• pixi global writes it into the exclude-newer of a new, empty global manifest. A global manifest created from an existing installation doesn't get it, as those environments were installed without a cutoff.
• pixi exec solves its environments with it. The cached exec environment is keyed by the configured value (a relative cutoff stays 7d, like in fix: reuse the build backend environment with a relative exclude-newer #7384), and only when it is set, so existing exec environments keep their names.

The key is part of the configuration shared by all rattler-based tools (conda/rattler#3020), so it can also be set in a rattler config file and rattler-build can use it as well. rattler_config keeps the cutoff and exemptions as written; pixi parses them with the manifest's own exclude-newer parser via the new ExcludeNewerConfig::from_toml_value, so they have the same syntax and errors.

Note

The rattler crates point to the commit of conda/rattler#3020 on a fork for now. This will be replaced with the released version of rattler_config before merging. pixi config set exclude-newer 7d sets a cutoff, and a table is given as JSON like the other complex config values.

Per-channel cutoffs for default-channels (the other idea in #5810) are not part of this, as default-channels only takes channel names.

How Has This Been Tested?

• Unit tests for parsing both forms from the config and for pixi config set/unset.
• Unit test that the exec environment hash depends on the configured value.
• Integration tests: pixi init writes the configured cutoff and exemptions; pixi exec fails with a cutoff before every package of the test channel and succeeds once the package is exempted; pixi global install writes the default into the new global manifest and applies the cutoff to packages that are not exempted.

AI Disclosure

• This PR contains AI-generated content.
  • I have tested any AI-generated content in my PR.
  • I take responsibility for any AI-generated content in my PR.

Tools: Claude Code

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added sufficient tests to cover my changes.
• I have verified that changes that would impact the JSON schema have been made in schema/model.py.

[wolfv]

Shouldn't or couldn't this go to the rattler configuration so that we can use it in rattler-build as well?

[pavelzw]

yes you are right. was too late for me yesterday night i guess...

[pavelzw]

conda/rattler#3020

[pavelzw]

depends on prefix-dev/rattler-build#2914

[lucascolley]

I found a few more things that we might want to change in rattler, so no rush on that release... nothing hugely blocking but seems like we would still have some workarounds on the Pixi side

[lucascolley]

thank you for working through this, Pavel!