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-09-02T22:05:15Z",
-  "commit_sha": "bb2e54da3483cf81aec983b30038a39df0cb2609"
+  "updated_at": "2025-09-09T22:05:41Z",
+  "commit_sha": "00bc842062c0b56933528d68d59c93f1a252987a"
 }

src/assets/pixi/deployment/container.md

@@ -11,7 +11,8 @@ There are different tags for different base images available:
 - `latest` - based on `ubuntu:jammy`
 - `focal` - based on `ubuntu:focal`
 - `bullseye` - based on `debian:bullseye`
-- `jammy-cuda-12.2.2` - based on `nvidia/cuda:12.2.2-jammy`
+- `noble-cuda-12.9.1` - based on `nvidia/cuda:12.9.1-base-ubuntu24.04`
+- `noble-cuda-13.0.0` - based on `nvidia/cuda:13.0.0-base-ubuntu24.04`
 - ... and more
 
 !!!tip "All tags"

src/assets/pixi/integration/ci/github_actions.md

@@ -10,7 +10,7 @@ We created [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi) to
 ```yaml
 - uses: prefix-dev/setup-pixi@v0.9.0
   with:
-    pixi-version: v0.54.0
+    pixi-version: v0.54.2
     cache: true
     auth-host: prefix.dev
     auth-token: ${{ secrets.PREFIX_DEV_TOKEN }}

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

@@ -28,7 +28,7 @@ Then, create the following two files in the `.devcontainer` directory:
 ```dockerfile title=".devcontainer/Dockerfile"
 FROM mcr.microsoft.com/devcontainers/base:jammy
 
-ARG PIXI_VERSION=v0.54.0
+ARG PIXI_VERSION=v0.54.2
 
 RUN curl -L -o /usr/local/bin/pixi -fsSL --compressed "https://github.com/prefix-dev/pixi/releases/download/${PIXI_VERSION}/pixi-$(uname -m)-unknown-linux-musl" \
     && chmod +x /usr/local/bin/pixi \

src/assets/pixi/integration/extensions/introduction.md

@@ -23,7 +23,7 @@ Pixi searches all directories in your `PATH` environment variable for executable
 ### 2. `pixi global` Directories  
 Pixi also searches in directories managed by `pixi global`, which allows for organized extension management without cluttering your system PATH.
 
-When you run `pixi --help`, all discovered extensions are automatically listed in the "Available Extensions" section, making them easily discoverable alongside built-in commands.
+When you run `pixi --list`, all discovered extensions are automatically listed alongside all built-in commands, making the commands easily discoverable.
 
 ## Installing Extensions
 
@@ -43,7 +43,7 @@ This approach has several advantages:
 - **Isolated environments**: Each extension gets its own environment, preventing dependency conflicts
 - **Automatic discovery**: Extensions are automatically found by Pixi without modifying PATH
 - **Easy management**: Use `pixi global list` and `pixi global remove` to manage extensions
-- **Consistent experience**: Extensions appear in `pixi --help` just like built-in commands
+- **Consistent experience**: Extensions appear in `pixi --list` with all the built-in commands, just like how `Cargo` handles it
 
 ### Manual Installation
 
@@ -105,7 +105,7 @@ This works for both built-in commands and any extensions you have installed, mak
 
 ## Getting Help
 
-- **List available extensions**: Run `pixi --help` to see all available extensions
+- **List available extensions**: Run `pixi --list` to see all available extensions
 - **Community**: Join our [Discord](https://discord.gg/kKV8ZxyzY4) for discussions and support
 
 ## See Also

src/assets/pixi/reference/cli/pixi/add.md

@@ -64,16 +64,12 @@ pixi add [OPTIONS] <SPEC>...
 ## Update Options
 - <a id="arg---no-install" href="#arg---no-install">`--no-install`</a>
 :  Don't modify the environment, only modify the lock-file
-- <a id="arg---frozen" href="#arg---frozen">`--frozen=<FROZEN>`</a>
+- <a id="arg---frozen" href="#arg---frozen">`--frozen`</a>
 :  Install the environment as defined in the lockfile, doesn't update lockfile if it isn't up-to-date with the manifest file
 <br>**env**: `PIXI_FROZEN`
-<br>**default**: `false`
-<br>**options**: `true`, `false`
-- <a id="arg---locked" href="#arg---locked">`--locked=<LOCKED>`</a>
+- <a id="arg---locked" href="#arg---locked">`--locked`</a>
 :  Check if lockfile is up-to-date before installing the environment, aborts when lockfile isn't up-to-date with the manifest file
 <br>**env**: `PIXI_LOCKED`
-<br>**default**: `false`
-<br>**options**: `true`, `false`
 
 ## Global Options
 - <a id="arg---manifest-path" href="#arg---manifest-path">`--manifest-path <MANIFEST_PATH>`</a>

src/assets/pixi/reference/cli/pixi/auth/login.md

@@ -13,7 +13,7 @@ pixi auth login [OPTIONS] <HOST>
 
 ## Arguments
 - <a id="arg-<HOST>" href="#arg-<HOST>">`<HOST>`</a>
-:  The host to authenticate with (e.g. repo.prefix.dev)
+:  The host to authenticate with (e.g. prefix.dev)
 <br>**required**: `true`
 
 ## Options

src/assets/pixi/reference/cli/pixi/install.md

@@ -48,16 +48,12 @@ pixi install [OPTIONS]
 :  Use environment activation cache (experimental)
 
 ## Update Options
-- <a id="arg---frozen" href="#arg---frozen">`--frozen=<FROZEN>`</a>
+- <a id="arg---frozen" href="#arg---frozen">`--frozen`</a>
 :  Install the environment as defined in the lockfile, doesn't update lockfile if it isn't up-to-date with the manifest file
 <br>**env**: `PIXI_FROZEN`
-<br>**default**: `false`
-<br>**options**: `true`, `false`
-- <a id="arg---locked" href="#arg---locked">`--locked=<LOCKED>`</a>
+- <a id="arg---locked" href="#arg---locked">`--locked`</a>
 :  Check if lockfile is up-to-date before installing the environment, aborts when lockfile isn't up-to-date with the manifest file
 <br>**env**: `PIXI_LOCKED`
-<br>**default**: `false`
-<br>**options**: `true`, `false`
 
 ## Global Options
 - <a id="arg---manifest-path" href="#arg---manifest-path">`--manifest-path <MANIFEST_PATH>`</a>

src/assets/pixi/reference/cli/pixi/list.md

@@ -32,16 +32,12 @@ pixi list [OPTIONS] [REGEX]
 :  Only list packages that are explicitly defined in the workspace
 
 ## Update Options
-- <a id="arg---frozen" href="#arg---frozen">`--frozen=<FROZEN>`</a>
+- <a id="arg---frozen" href="#arg---frozen">`--frozen`</a>
 :  Install the environment as defined in the lockfile, doesn't update lockfile if it isn't up-to-date with the manifest file
 <br>**env**: `PIXI_FROZEN`
-<br>**default**: `false`
-<br>**options**: `true`, `false`
-- <a id="arg---locked" href="#arg---locked">`--locked=<LOCKED>`</a>
+- <a id="arg---locked" href="#arg---locked">`--locked`</a>
 :  Check if lockfile is up-to-date before installing the environment, aborts when lockfile isn't up-to-date with the manifest file
 <br>**env**: `PIXI_LOCKED`
-<br>**default**: `false`
-<br>**options**: `true`, `false`
 - <a id="arg---no-install" href="#arg---no-install">`--no-install`</a>
 :  Don't modify the environment, only modify the lock-file
 

src/assets/pixi/reference/cli/pixi/reinstall.md

@@ -44,16 +44,12 @@ pixi reinstall [OPTIONS] [PACKAGE]...
 :  Use environment activation cache (experimental)
 
 ## Update Options
-- <a id="arg---frozen" href="#arg---frozen">`--frozen=<FROZEN>`</a>
+- <a id="arg---frozen" href="#arg---frozen">`--frozen`</a>
 :  Install the environment as defined in the lockfile, doesn't update lockfile if it isn't up-to-date with the manifest file
 <br>**env**: `PIXI_FROZEN`
-<br>**default**: `false`
-<br>**options**: `true`, `false`
-- <a id="arg---locked" href="#arg---locked">`--locked=<LOCKED>`</a>
+- <a id="arg---locked" href="#arg---locked">`--locked`</a>
 :  Check if lockfile is up-to-date before installing the environment, aborts when lockfile isn't up-to-date with the manifest file
 <br>**env**: `PIXI_LOCKED`
-<br>**default**: `false`
-<br>**options**: `true`, `false`
 
 ## Global Options
 - <a id="arg---manifest-path" href="#arg---manifest-path">`--manifest-path <MANIFEST_PATH>`</a>