pixi update#

Updates dependencies to newer compatible versions

Usage#

pixi update [OPTIONS] [PACKAGES]...

Arguments#

• <PACKAGES>

  The packages to update, space separated. If no packages are provided, all packages will be updated
  May be provided more than once.

Options#

• --no-install

  Don't install the (solve) environments needed for pypi-dependencies solving
  env: PIXI_NO_INSTALL

• --dry-run (-n)

  Don't write the updated resolution or update any environment

• --environment (-e) <ENVIRONMENT>

  The environments to update. If none is specified, all environments are updated
  May be provided more than once.

• --platform (-p) <PLATFORM>

  The platforms to update. If none is specified, all platforms are updated. Accepts a workspace platform name; a bare conda subdir (e.g. linux-64) is also accepted so users don't have to declare a platform before targeting it
  May be provided more than once.

• --json

  Output the changes in JSON format

Config Options#

• --no-config

  Don't read system or user-level configuration files. Project-local <project>/.pixi/config.toml is still loaded
  env: PIXI_NO_CONFIG
  default: false

• --config-file <PATH>

  Load configuration from this file instead of searching system and user-level paths. Project-local <project>/.pixi/config.toml is still merged on top
  env: PIXI_CONFIG_FILE

• --auth-file <AUTH_FILE>

  Path to the file containing the authentication token

• --concurrent-downloads <CONCURRENT_DOWNLOADS>

  Max concurrent network requests, default is 50

• --concurrent-solves <CONCURRENT_SOLVES>

  Max concurrent solves, default is the number of CPUs

• --pinning-strategy <PINNING_STRATEGY>

  Set pinning strategy
  options: semver, minor, major, latest-up, exact-version, no-pin

• --pypi-keyring-provider <PYPI_KEYRING_PROVIDER>

  Specifies whether to use the keyring to look up credentials for PyPI
  options: disabled, subprocess

• --run-post-link-scripts

  Run post-link scripts (insecure)

• --no-symbolic-links

  Disallow symbolic links during package installation
  env: PIXI_NO_SYMBOLIC_LINKS

• --no-hard-links

  Disallow hard links during package installation
  env: PIXI_NO_HARD_LINKS

• --no-ref-links

  Disallow ref links (copy-on-write) during package installation
  env: PIXI_NO_REF_LINKS

• --tls-no-verify

  Do not verify the TLS certificate of the server

• --offline=<OFFLINE>

  Run without network access, using only cached data. Commands fail if data is missing from the cache. Pass --offline=false to override an offline setting from the configuration
  env: PIXI_OFFLINE
  options: y, yes, t, true, on, 1, n, no, f, false, off, 0

• --tls-root-certs <TLS_ROOT_CERTS>

  Which TLS root certificates to use: 'webpki' (bundled Mozilla roots) or 'system' (system store)
  env: PIXI_TLS_ROOT_CERTS

• --use-environment-activation-cache

  Use environment activation cache (experimental)

Global Options#

• --manifest-path (-m) <MANIFEST_PATH>

  The path to pixi.toml, pyproject.toml, or the workspace directory

• --workspace (-w) <WORKSPACE>

  Name of the workspace

• --script (-s) <SCRIPT>

  The path to a script with an embedded manifest: a Python script containing PEP 723 metadata, or a file of any language containing a /// conda-script block

Description#

Updates dependencies to newer compatible versions.

Projects and scripts with an adjacent lock file write that lock file. A script without one writes its cached resolution.

Examples#

pixi update numpy # (1)!
pixi update numpy pandas # (2)!
pixi update --manifest-path ~/myworkspace/pixi.toml numpy # (3)!
pixi update --environment lint python # (4)!
pixi update -e lint -e schema -e docs pre-commit # (5)!
pixi update --platform osx-arm64 mlx # (6)!
pixi update -p linux-64 -p osx-64 numpy  # (7)!
pixi update --dry-run numpy # (8)!
pixi update --no-install boto3 # (9)!

1. This will update the numpy package to the latest version that fits the requirement.
2. This will update the numpy and pandas packages to the latest version that fits the requirement.
3. This will update the numpy package to the latest version in the manifest file at the given path.
4. This will update the python package in the lint environment.
5. This will update the pre-commit package in the lint, schema, and docs environments.
6. This will update the mlx package in the osx-arm64 platform.
7. This will update the numpy package in the linux-64 and osx-64 platforms.
8. This will show the packages that would be updated without actually updating them in the lock file
9. This will update the boto3 package in the manifest and lock file, without installing it in an environment.