Documentation Index
Fetch the complete documentation index at: https://mintlify.com/conda/conda/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Theconda update command updates conda packages to the latest compatible version. It accepts a list of package names and updates them to the latest versions that are compatible with all other packages in the environment.
Conda attempts to install the newest versions of the requested packages. To accomplish this, it may update some packages that are already installed, or install additional packages.
Syntax
Target Environment Specification
Name of environment.
Full path to environment location (i.e. prefix).
Package Specifications
List of packages to update in the conda environment. Package specifications can include:
- Simple names:
numpy - Version constraints:
python>=3.11,numpy>=1.20
Read package versions from the given file. Repeated file specifications can be passed (e.g.
--file=file1 --file=file2).Solver Mode Modifiers
Do not update or change already-installed dependencies. This may force conda to install older versions of the requested packages.
Update dependencies that have available updates.
Exit early and do not run the solver if the requested specs are satisfied. Also skips aggressive updates as configured by the
aggressive_update_packages config setting.Update all installed packages in the environment.
Update based on provided specifications.
Do not install, update, remove, or change dependencies. This WILL lead to broken environments and inconsistent behavior. Use at your own risk.
Only update dependencies.
Ensure that any user-requested package for the current operation is uninstalled and reinstalled, even if that package already exists in the environment.
Ignore pinned file.
Packages in lower priority channels are not considered if a package with the same name appears in a higher priority channel.
Package version takes precedence over channel priority. Overrides the value given by
conda config --show channel_priority.Choose which solver backend to use.
Channel Customization
Additional channel to search for packages. These are URLs searched in the order they are given (including local directories using the
file:// syntax or simply a path like /home/conda/mychan or ../mychan). Can be used multiple times.Use locally built packages. Identical to
-c local.Do not search default or .condarc channels. Requires —channel.
Specify file name of repodata on the remote server. Can be passed multiple times.
Enable experimental features. Options:
jlap (download incremental package index data), lock (use locking when reading/updating index cache).Disable locking when reading, updating index (repodata.json) cache.
Check for/do not check for repodata.json.zst. Enabled by default.
Package Linking and Install-time Options
Allow clobbering of overlapping file paths within packages, and suppress related warnings.
Install all packages using copies instead of hard- or soft-linking.
Don’t install start menu shortcuts.
Install shortcuts only for this package name. Can be used several times.
Networking Options
Use cache of channel index files, even if it has expired. This is useful if you don’t want conda to check whether a new version of the repodata file exists.
Allow conda to perform “insecure” SSL connections and transfers. Equivalent to setting
ssl_verify to false.Offline mode. Don’t connect to the Internet.
Output, Prompt, and Flow Control Options
Solve an environment and ensure package caches are populated, but exit prior to unlinking and linking packages into the prefix.
Show channel urls. Overrides the value given by
conda config --show show_channel_urls.Report all output as json. Suitable for using conda programmatically.
Can be used multiple times. Once for detailed output, twice for INFO logging, thrice for DEBUG logging, four times for TRACE logging.
Do not display progress bar.
Only display what would have been done.
Sets any confirmation values to ‘yes’ automatically. Users will not be asked to confirm any adding, deleting, backups, etc.
Environment Protection
DANGEROUS. Use at your own risk. Ignore protections if the environment is frozen.
Examples
Common Use Cases
Updating All Packages in an Environment
Update all packages to their latest compatible versions:Updating Conda Itself
Keep your conda installation up to date:Updating Specific Packages
Update one or more specific packages:Updating Without Breaking Dependencies
Use--no-update-deps to update only the specified package:
Checking What Would Be Updated
Use dry-run mode to preview changes:Updating with Dependency Updates
Explicitly update dependencies:If you wish to prevent existing packages from updating, use the
--no-update-deps option. This may force conda to install older versions of the requested packages, and it does not prevent additional dependency packages from being installed.