Skip to main content
The pixi update command updates the lock file to use newer versions of dependencies while respecting manifest constraints.

Usage

Overview

The pixi update command:
  1. Unlocks specified packages in the lock file
  2. Re-resolves dependencies to find newer versions
  3. Updates the lock file with new versions
  4. Installs updated environments (unless --no-install)
pixi update respects version constraints in your manifest. It will only update to versions that satisfy your specifications.

Arguments

string
Specific package(s) to update. If not provided, all packages are updated.

Options

Environment Filter

string
Update only in specific environment(s). Can be specified multiple times.Short flag: -e

Platform Filter

string
Update only for specific platform(s). Can be specified multiple times.Short flag: -p

Installation Control

boolean
default:"false"
Update lock file without installing. Useful for batch updates.
boolean
default:"false"
Show what would be updated without making changes.Short flag: -n

Output Format

boolean
default:"false"
Output changes in JSON format.

Examples

Update All Packages

Output:

Update Specific Package

Output:

Update Multiple Packages

Output:

Update for Specific Environment

Output:

Update for Specific Platform

Output:

Dry Run

See what would be updated without making changes:
Output:

JSON Output

Output:

No Changes

When already up-to-date:
Output:

Behavior Details

Version Constraint Respect

Manifest:
Result: Updates to latest 1.x version (e.g., 1.26.4), not 2.0+

Dependency Updates

Updating a package also updates its dependencies:
May also update:
  • numpy (pandas dependency)
  • python-dateutil (pandas dependency)
  • Other transitive dependencies

Platform-Specific Updates

With platform-specific dependencies:
Only updates cuda and linux-64 packages, not metal.

Environment-Specific Updates

Only updates packages in the test environment.

Combining Filters

Package + Environment

Updates numpy only in the prod environment.

Package + Platform

Updates cuda only for linux-64 platform.

Environment + Platform

Updates all packages in prod environment on linux-64 platform.

All Filters Combined

Updates numpy and pandas in prod environment for linux-64, without installing.

Update vs Upgrade

pixi update and pixi upgrade are different commands:

Use Cases

Regular Maintenance

Keep dependencies up-to-date:

Security Patches

Update specific vulnerable package:

Pre-Production Testing

Test updates without affecting dev:

CI/CD Integration

Automated update checks:

Multi-Platform Maintenance

Update each platform separately:

Global Options

string
Path to pixi.toml, pyproject.toml, or workspace directory.Short flag: -m

Config Options

  • --auth-file <FILE>: Authentication credentials
  • --tls-no-verify: Disable TLS verification
  • --concurrent-solves <N>: Max concurrent solves

Troubleshooting

Package Not Found

Error: could not find a package named 'numpyy' Solution: Check spelling and verify package is in lock file:
Suggestions will be provided:

No Updates Available

Output:
Package is already at the latest version satisfying constraints.

Version Constraints Too Strict

Manifest:
Output:
Solution: Loosen constraints or use pixi upgrade:

Solver Conflicts

Error: cannot solve dependencies Solution: Update conflicting packages together:
Or check manifest constraints:

Environment Not Found

Error: could not find an environment named 'production' Solution: Check environment names:
Use correct environment name:

Best Practices

  1. Update regularly to get security patches:
  2. Test after updates:
  3. Use dry-run first for large projects:
  4. Update environments separately in multi-env projects:
  5. Commit lock file changes:
  6. Use CI to detect updates:

See Also