docs(src/assets/): update conda official documentation

Author: KemingHe

src/assets/conda/_metadata.json

@@ -1,6 +1,6 @@
 {
   "source_repo": "conda/conda",
   "docs_path": "docs",
-  "updated_at": "2025-11-04T22:05:04Z",
-  "commit_sha": "a971401092e0ab6c770d5ea985611fd001cfe974"
+  "updated_at": "2025-11-11T22:05:38Z",
+  "commit_sha": "0049f3a2eae767641bf8be5340f6e40572797197"
 }

src/assets/conda/source/user-guide/configuration/settings.rst

@@ -649,6 +649,38 @@ or specify it on the command line with the ``--console`` option
 
    conda info --console=colors
 
+.. _override-virtual-packages:
+
+``override_virtual_packages``: Set version or build variables for virtual packages
+----------------------------------------------------------------------------------
+
+.. note::
+   You can also use ``virtual_packages`` for this setting.
+
+The ``override_virtual_packages`` setting is a dictionary that allows you set
+specific version or build overrides for virtual package installs.
+
+Conda sets virtual package version and/or build numbers in three ways:
+
+1. By passing an enviroment variable with the ``conda install`` command (highest priority)
+
+   For example: ``CONDA_OVERRIDE_CUDA="12.0" conda install -c conda-forge tensorflow``
+
+1. The ``override_virtual_packages`` dictionary in the ``.condarc`` file
+
+1. The variables set up in the virtual package's code (lowest priority)
+
+For more information on virtual packages, see :ref:`Managing virtual packages <manage-virtual>`.
+
+Your ``override_virtual_packages`` dictionary could look like the following:
+
+.. code-block:: yaml
+
+    override_virtual_packages:
+      cuda: "12.8"
+      glbc: "2.17"
+      osx: "11.0"
+      archspec: "x86_64"
 
 Conda-build configuration
 =========================

src/assets/conda/source/user-guide/tasks/manage-virtual.rst

@@ -71,11 +71,54 @@ Overriding detected packages
 ============================
 
 For troubleshooting, it is possible to override virtual package detection
-using an environment variable. Supported variables include:
-
-* ``CONDA_OVERRIDE_CUDA`` - CUDA version number or set to ``""`` for no CUDA
-  detected.
-* ``CONDA_OVERRIDE_OSX`` - OSX version number or set to ``""`` for no OSX
-  detected.
-* ``CONDA_OVERRIDE_GLIBC`` - GLIBC version number or set to ``""`` for no GLIBC.
-  This only applies on Linux.
+using an environment variable or a setting in your ``.condarc`` file.
+
+Environment variables
+---------------------
+
+You can set environment variables when using a ``conda install`` command.
+This way of overriding has the highest priority, **but the override
+variable must be set every time a package requiring that override is installed**.
+
+**Example**:
+
+.. code-block::
+
+    CONDA_OVERRIDE_CUDA=12.8 conda install pytorch
+
+Supported variables include:
+
+.. csv-table::
+    :header-rows: 1
+
+    Variable Name, Override Entity, Example
+    ``CONDA_OVERRIDE_ARCHSPEC``, Build Number, x86_64
+    ``CONDA_OVERRIDE_CUDA``, Version Number, 12.8
+    ``CONDA_OVERRIDE_GLIBC``, Version Number, 2.17
+    ``CONDA_OVERRIDE_LINUX``, Version Number, 5.15.0
+    ``CONDA_OVERRIDE_OSX``, Version Number, 11.0
+    ``CONDA_OVERRIDE_WIN``, Version Number, 10.0.22631
+
+.. note::
+
+    For any custom virtual packages, the variable name is
+    ``CONDA_OVERRIDE_<NAME>`` and the override entity is the
+    ``override_entity`` variable value, either "version" or "build".
+
+``.condarc`` setting
+--------------------
+
+To avoid having to set any override variables every time you install a package,
+conda also offers the ability to set these overrides in your ``.condarc`` file.
+
+.. code-block:: yaml
+
+    override_virtual_packages:
+      archspec: "x86_64"
+      cuda: "12.8"
+      glibc: "2.17"
+      osx: "11.0"
+      mycustompackage: "1.2.3"
+
+See :ref:`override-virtual-packages <override-virtual-packages>` for more information on
+the ``.condarc`` setting.