Skip to content

pixi workspace exclude-newer exempt#

Exempt package releases from the cutoff.

Usage#

pixi workspace exclude-newer exempt [OPTIONS] <SPEC>...

Arguments#

  • <SPEC>
    The releases to exempt, e.g. python, python=3.13.* or conda-forge::ruff. PyPI exemptions only take package names
    May be provided more than once.
    required: true

Options#

  • --cutoff <CUTOFF>
    Only exempt the releases published up to this cutoff: now, an RFC 3339 timestamp, a date like 2026-01-01, which includes the whole day in UTC, or a duration like 7d, which moves with the current time. Defaults to now for specs with a version, e.g. openssl==3.2.1
  • --no-cutoff
    Exempt every matching release, including the ones published in the future
  • --pypi
    Edit pypi-exclude-newer, which applies to PyPI packages, instead of exclude-newer. Locked PyPI packages are not re-solved, run pixi update for that

Config Options#

Update Options#

  • --no-install
    Don't modify the environment, only modify the lock file
    env: PIXI_NO_INSTALL
  • --frozen
    Install the environment as defined in the lock file, doesn't update lock file if it isn't up-to-date with the manifest file
    env: PIXI_FROZEN
  • --locked
    Check if lock file is up-to-date before installing the environment, aborts when lock file isn't up-to-date with the manifest file
    env: PIXI_LOCKED

Description#

Exempt package releases from the cutoff.

Exemptions are match specs, a bare package name exempts every release. A package has a single exemption, so to exempt several versions, combine them in one spec, e.g. python==3.11.18|==3.12.16. An existing exemption of the same package is replaced, with a warning if that moves its cutoff later.

An exemption with a version only exempts the releases that are already published, so e.g. a later build of an exempt version is not exempt.

Example: pixi workspace exclude-newer exempt openssl==3.2.1 conda-forge::ruff pixi workspace exclude-newer exempt openssl==3.2.1 --cutoff 2026-10-12