The pixi global upgrade-all command has been removed. Use pixi global update instead for updating all globally installed packages.
This command has been deprecated and removed. Use pixi global update instead.
Migration
Old Command
New Command
The pixi global update command provides the same functionality with improved features.
Why This Command Was Removed
The upgrade-all command was replaced by the more flexible update command which:
- Updates all environments by default (same as
upgrade-all)
- Allows updating specific environments
- Better handles environment state and exposures
- Provides more detailed output
- Has improved error handling
Replacement Examples
Update All Environments
Old:
New:
Update with Options
Old:
pixi global upgrade-all --platform linux-64
Error Message
If you try to run pixi global upgrade-all, you’ll see:
Error: `pixi global upgrade-all` has been removed
You can call `pixi global update` for most use cases
What Changed
The pixi global update command provides:
- Same default behavior: Updates all environments when no arguments provided
- Selective updates: Can update specific environments
- Better state management: Properly tracks exposure strategies
- Improved output: Shows detailed update information
Update All (Same as upgrade-all)
This updates all global environments, just like upgrade-all did.
Update Specific Environments (New Feature)
pixi global update python311 tools
upgrade-all.
Configuration
The old command used these options:
--channels: No longer needed, channels are read from manifest--platform: Automatically detected
These are now managed through the global manifest:
pixi global edit # Edit global manifest to configure channels
pixi global update # Update with those settings
Current Update Commands
pixi global update - Update all or specific environmentspixi global upgrade - (Also deprecated, use update)
Other Global Commands
pixi global install - Install new environmentspixi global list - List installed environmentspixi global sync - Sync environments without updating
Complete Migration Guide
Scenario 1: Regular Updates
Before:
# Weekly update routine
pixi global upgrade-all
# Same routine
pixi global update
# Had to update everything
pixi global upgrade-all
# Can update just what you need
pixi global update tools dev-tools
Scenario 3: With Custom Channels
Before:
pixi global upgrade-all --channels conda-forge,bioconda
# Configure channels in manifest first
pixi global edit
# Add channels to environments, then:
pixi global update
Scenario 4: Automation Scripts
Before:
#!/bin/bash
pixi global upgrade-all
#!/bin/bash
pixi global update
Frequently Asked Questions
Why was upgrade-all removed?
The command was redundant with pixi global update, which offers the same functionality and more.
Will my scripts break?
Yes, if they use pixi global upgrade-all. Update them to use pixi global update instead.
Is there any difference in behavior?
The core update behavior is the same, but pixi global update has:
- Better exposure handling
- More detailed output
- Ability to update specific environments
- Improved error messages
Can I still use the old command?
No, it has been completely removed. You must use pixi global update.
Upgrade Checklist
Update your workflows:
Benefits of the New Command
Selective Updates
# Update only critical environments
pixi global update prod
# Update everything
pixi global update
Better Output
✅ Updated environment python311
• python 3.11.7 -> 3.11.8
• pip 23.3.1 -> 24.0
✅ Updated environment tools
• ruff 0.1.9 -> 0.2.0
Improved Error Handling
✅ Updated environment python311
❌ Failed to update environment tools: version conflict
Reverting tools to previous state...
✅ Reverted environment tools
Timeline
The command was:
- Deprecated: Version 0.x.x
- Marked as hidden: Version 0.x.x
- Removed: Current version
Support
If you have issues migrating from upgrade-all to update:
- Check the pixi global update documentation
- Review your global manifest:
pixi global edit
- Test the update:
pixi global list before and after
See Also