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-10-28T22:05:52Z",
-  "commit_sha": "d1e724f8e37338c5b2d93277d39d0ef3fa5a7425"
+  "updated_at": "2025-11-04T22:05:36Z",
+  "commit_sha": "82061b47054e276ea428e3603fd15f3645e18ecb"
 }

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.2
   with:
-    pixi-version: v0.58.0
+    pixi-version: v0.59.0
     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.58.0
+ARG PIXI_VERSION=v0.59.0
 
 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/reference/cli/pixi.md

@@ -13,7 +13,7 @@ pixi [OPTIONS] [COMMAND]
 |---------|-------------|
 | [`add`](pixi/add.md) | Adds dependencies to the workspace |
 | [`auth`](pixi/auth.md) | Login to prefix.dev or anaconda.org servers to access private channels |
-| [`build`](pixi/build.md) | Workspace configuration |
+| [`build`](pixi/build.md) | Lock file and installation configuration with --as-is support Used by shell, shell-hook, and run commands |
 | [`clean`](pixi/clean.md) | Cleanup the environments |
 | [`completion`](pixi/completion.md) | Generates a completion script for a shell |
 | [`config`](pixi/config.md) | Configuration management |
@@ -23,7 +23,7 @@ pixi [OPTIONS] [COMMAND]
 | [`init`](pixi/init.md) | Creates a new workspace |
 | [`import`](pixi/import.md) | Imports a file into an environment in an existing workspace. |
 | [`install`](pixi/install.md) | Install an environment, both updating the lockfile and installing the environment |
-| [`list`](pixi/list.md) | List workspace's packages |
+| [`list`](pixi/list.md) | List the packages of the current workspace |
 | [`lock`](pixi/lock.md) | Solve environment and update the lock file without installing the environments |
 | [`reinstall`](pixi/reinstall.md) | Re-install an environment, both updating the lockfile and re-installing the environment |
 | [`remove`](pixi/remove.md) | Removes dependencies from the workspace |

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

@@ -2,7 +2,7 @@
 # <code>[pixi](../pixi.md) build</code>
 
 ## About
-Workspace configuration
+Lock file and installation configuration with --as-is support Used by shell, shell-hook, and run commands
 
 --8<-- "docs/reference/cli/pixi/build_extender:description"
 
@@ -46,6 +46,18 @@ pixi build [OPTIONS]
 - <a id="arg---use-environment-activation-cache" href="#arg---use-environment-activation-cache">`--use-environment-activation-cache`</a>
 :  Use environment activation cache (experimental)
 
+## 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`</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`
+- <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`
+- <a id="arg---as-is" href="#arg---as-is">`--as-is`</a>
+:  Shorthand for the combination of --no-install and --frozen
+
 ## Global Options
 - <a id="arg---manifest-path" href="#arg---manifest-path">`--manifest-path <MANIFEST_PATH>`</a>
 :  The path to `pixi.toml`, `pyproject.toml`, or the workspace directory

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

@@ -2,7 +2,7 @@
 # <code>[pixi](../pixi.md) list</code>
 
 ## About
-List workspace's packages
+List the packages of the current workspace
 
 --8<-- "docs/reference/cli/pixi/list_extender:description"
 
@@ -46,7 +46,7 @@ pixi list [OPTIONS] [REGEX]
 :  The path to `pixi.toml`, `pyproject.toml`, or the workspace directory
 
 ## Description
-List workspace's packages.
+List the packages of the current workspace
 
 Highlighted packages are explicit dependencies.
 

src/assets/pixi/reference/pixi_manifest.md

@@ -1067,19 +1067,46 @@ The build system is a table that can contain the following fields:
 
 - `source`: specifies the location of the source code for the package. Default: manifest directory. Currently supported options:
   - `path`: a string representing a relative or absolute path to the source code.
+  - `git`: a string representing URL to the source repository.
+  - `rev`: a string representing SHA revision to checkout.
+  - `subdirectory`: a string representing path to subdirectory to use.
 - `channels`: specifies the channels to get the build backend from.
 - `backend`: specifies the build backend to use. This is a table that can contain the following fields:
   - `name`: the name of the build backend to use. This will also be the executable name.
   - `version`: the version of the build backend to use.
-- `configuration`: a table that contains the configuration options for the build backend.
+- `config`: a table that contains the configuration options for the build backend.
 - `target`: a table that can contain target specific build configuration.
+  - Each target can have its own `config` table to override or extend the base configuration for specific platforms.
 
 More documentation on the backends can be found in the [build backend documentation](../build/backends.md).
 
+#### Basic build configuration example
+
 ```toml
 --8<-- "docs/source_files/pixi_tomls/pixi-package-manifest.toml:build-system"
 ```
 
+#### Target-specific build configuration example
+
+For platform-specific build configuration, use the `[package.build.target.<platform>]` table:
+
+```toml
+[package.build]
+backend = { name = "pixi-build-cmake", version = "0.3.*" }
+
+[package.build.config]
+# Base configuration applied to all platforms
+extra-args = ["-DCMAKE_BUILD_TYPE=Release"]
+
+[package.build.target.linux-64.config]
+# Linux-specific configuration
+extra-args = ["-DCMAKE_BUILD_TYPE=Debug", "-DLINUX_FLAG=ON"]
+
+[package.build.target.win-64.config]
+# Windows-specific configuration
+extra-args = ["-DCMAKE_BUILD_TYPE=Debug", "-DWIN_FLAG=ON"]
+```
+
 
 ### The `build` `host` and `run` dependencies tables
 The dependencies of a package are split into three tables.

src/assets/pixi/tutorials/rust.md

@@ -124,7 +124,7 @@ compilation process.
 Make sure you also have the development packages of openssl installed.
 For example, `libssl-dev` on Ubuntu or `openssl-devel` on Fedora.
 
-If you're in a situation where you think the directory *should* be found
+If you are in a situation where you think the directory *should* be found
 automatically, please open a bug at https://github.com/sfackler/rust-openssl
 and include information about your system as well as this message.
 
@@ -133,7 +133,7 @@ $TARGET = x86_64-unknown-linux-gnu
 openssl-sys = 0.9.102
 
 
-It looks like you're compiling on Linux and also targeting Linux. Currently this
+It looks like you are compiling on Linux and also targeting Linux. Currently this
 requires the `pkg-config` utility to find OpenSSL but unfortunately `pkg-config`
 could not be found. If you have OpenSSL installed you can likely fix this by
 installing `pkg-config`.