pixi update command updates the lock file to use newer versions of dependencies while respecting manifest constraints.
Usage
Overview
Thepixi update command:
- Unlocks specified packages in the lock file
- Re-resolves dependencies to find newer versions
- Updates the lock file with new versions
- 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
Specific package(s) to update. If not provided, all packages are updated.
Options
Environment Filter
Update only in specific environment(s). Can be specified multiple times.Short flag:
-ePlatform Filter
Update only for specific platform(s). Can be specified multiple times.Short flag:
-pInstallation Control
Update lock file without installing. Useful for batch updates.
Show what would be updated without making changes.Short flag:
-nOutput Format
Output changes in JSON format.
Examples
Update All Packages
Update Specific Package
Update Multiple Packages
Update for Specific Environment
Update for Specific Platform
Dry Run
See what would be updated without making changes:JSON Output
No Changes
When already up-to-date:Behavior Details
Version Constraint Respect
Manifest:Dependency Updates
Updating a package also updates its dependencies:numpy(pandas dependency)python-dateutil(pandas dependency)- Other transitive dependencies
Platform-Specific Updates
With platform-specific dependencies:cuda and linux-64 packages, not metal.
Environment-Specific Updates
test environment.
Combining Filters
Package + Environment
numpy only in the prod environment.
Package + Platform
cuda only for linux-64 platform.
Environment + Platform
prod environment on linux-64 platform.
All Filters Combined
numpy and pandas in prod environment for linux-64, without installing.
Update vs Upgrade
pixi update and pixi upgrade are different commands:| Feature | pixi update | pixi upgrade |
|---|---|---|
| Modifies manifest | No | Yes |
| Respects constraints | Yes | Loosens constraints |
| Updates lock file | Yes | Yes |
| Use case | Regular updates | Major version bumps |
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
Path to
pixi.toml, pyproject.toml, or workspace directory.Short flag: -mConfig 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:
No Updates Available
Version Constraints Too Strict
Manifest:pixi upgrade:
Solver Conflicts
Error:cannot solve dependencies
Solution: Update conflicting packages together:
Environment Not Found
Error:could not find an environment named 'production'
Solution: Check environment names:
Best Practices
-
Update regularly to get security patches:
-
Test after updates:
-
Use dry-run first for large projects:
-
Update environments separately in multi-env projects:
-
Commit lock file changes:
-
Use CI to detect updates:
See Also
- pixi upgrade - Upgrade dependencies with manifest changes
- pixi install - Install dependencies
- pixi add - Add new dependencies