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

Author: KemingHe

src/assets/pixi/_metadata.json

@@ -1,6 +1,6 @@
 {
   "source_repo": "prefix-dev/pixi",
   "docs_path": "docs",
-  "updated_at": "2025-11-25T22:05:53Z",
-  "commit_sha": "6638d0a3b70ab87c3968adc4b31ab796b9a3c0c1"
+  "updated_at": "2025-12-02T22:05:47Z",
+  "commit_sha": "9cfcecf4218fb4b2dda8fbbd70c367a1965c6427"
 }

src/assets/pixi/integration/editor/vscode.md

@@ -55,7 +55,7 @@ RUN echo 'eval "$(pixi completion -s bash)"' >> /home/vscode/.bashrc
       }
     },
     "features": {
-      "ghcr.io/devcontainers/environments/docker-in-docker:2": {}
+      "ghcr.io/devcontainers/features/docker-in-docker:2": {}
     },
     "mounts": ["source=${localWorkspaceFolderBasename}-pixi,target=${containerWorkspaceFolder}/.pixi,type=volume"],
     "postCreateCommand": "sudo chown vscode .pixi && pixi install"

src/assets/pixi/reference/pixi_manifest.md

@@ -444,6 +444,7 @@ The options that can be defined are:
 - `no-build`: don't build source distributions.
 - `no-binary`: don't use pre-build wheels.
 - `index-strategy`: allows for specifying the index strategy to use.
+- `prerelease-mode`: controls whether pre-release versions are allowed during dependency resolution.
 
 These options are explained in the sections below. Most of these options are taken directly or with slight modifications from the [uv settings](https://docs.astral.sh/uv/reference/settings/). If any are missing that you need feel free to create an issue [requesting](https://github.com/prefix-dev/pixi/issues) them.
 
@@ -571,6 +572,30 @@ By default, `uv` and thus `pixi`, will stop at the first index on which a given
 !!! info "PyPI only"
     The `index-strategy` only changes PyPI package resolution and not conda package resolution.
 
+
+### Prerelease Mode
+
+The strategy to use when considering pre-release versions during dependency resolution. Description taken from the [uv documentation](https://docs.astral.sh/uv/reference/settings/#prerelease).
+
+By default, `pixi` will allow pre-release versions when a package only has pre-release versions available, or when a pre-release version is explicitly requested in the version specifier (e.g., `>=1.0.0a1`).
+
+!!! warning "One prerelease mode per environment"
+    Only one `prerelease-mode` can be defined per environment or solve-group, otherwise, an error will be shown.
+
+#### Possible values:
+
+- **"disallow"**: Disallow all pre-release versions.
+- **"allow"**: Allow all pre-release versions.
+- **"if-necessary"**: Allow pre-release versions if all versions of a package are pre-release.
+- **"explicit"**: Allow pre-release versions for first-party packages with explicit pre-release markers in their version requirements.
+- **"if-necessary-or-explicit"** (default): Allow pre-release versions if all versions of a package are pre-release, or if the package has an explicit pre-release marker in its version requirements.
+
+Example:
+```toml
+[pypi-options]
+prerelease-mode = "allow"  # Allow all pre-release versions
+```
+
 ## The `dependencies` table(s)
 ??? info "Details regarding the dependencies"
     For more detail regarding the dependency types, make sure to check the [Run, Host, Build](../build/dependency_types.md) dependency documentation.