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": "2026-01-20T22:06:21Z",
-  "commit_sha": "c291577dcf9f9e85df7fe417cb472c5eb8e15199"
+  "updated_at": "2026-01-27T22:06:40Z",
+  "commit_sha": "bb5e1f751a0a5a0e62daea6157deae61f8e7c844"
 }

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

@@ -19,6 +19,8 @@ pixi run [OPTIONS] [TASK]...
 <br>May be provided more than once.
 
 ## Options
+- <a id="arg---executable" href="#arg---executable">`--executable (-x)`</a>
+:  Execute the command as an executable without resolving Pixi tasks
 - <a id="arg---environment" href="#arg---environment">`--environment (-e) <ENVIRONMENT>`</a>
 :  The environment to run the task in
 - <a id="arg---clean-env" href="#arg---clean-env">`--clean-env`</a>

src/assets/pixi/reference/pixi_manifest.md

@@ -401,14 +401,15 @@ Pixi's tasks are run in a Pixi environment using `pixi run` and are executed usi
 ```toml
 [tasks]
 simple = "echo This is a simple task"
-cmd = { cmd="echo Same as a simple task but now more verbose"}
-depending = { cmd="echo run after simple", depends-on="simple"}
-alias = { depends-on=["depending"]}
-download = { cmd="curl -o file.txt https://example.com/file.txt" , outputs=["file.txt"]}
-build = { cmd="npm build", cwd="frontend", inputs=["frontend/package.json", "frontend/*.js"]}
-run = { cmd="python run.py $ARGUMENT", env={ ARGUMENT="value" }}
+cmd = { cmd="echo Same as a simple task but now more verbose" }
+depending = { cmd="echo run after simple", depends-on="simple" }
+alias = { depends-on=["depending"] }
+download = { cmd="curl -o file.txt https://example.com/file.txt" , outputs=["file.txt"] }
+build = { cmd="npm build", cwd="frontend", inputs=["frontend/package.json", "frontend/*.js"] }
+run = { cmd="python run.py $ARGUMENT", env={ ARGUMENT="value" }} # Set an environment variable
 format = { cmd="black $INIT_CWD" } # runs black where you run pixi run format
-clean-env = { cmd = "python isolated.py", clean-env = true} # Only on Unix!
+clean-env = { cmd="python isolated.py", clean-env=true } # Only on Unix!
+test = { cmd="pytest", default-environment="test" }  # Set a default pixi environment
 ```
 
 You can modify this table using [`pixi task`](cli/pixi/task.md).
@@ -461,6 +462,7 @@ The options that can be defined are:
 - `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.
+- `skip-wheel-filename-check`: allows installing wheels with version mismatches between filename and metadata.
 
 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.
 
@@ -621,6 +623,39 @@ Example:
 prerelease-mode = "allow"  # Allow all pre-release versions
 ```
 
+### Skip Wheel Filename Check
+
+By default, `uv` validates that wheel filenames match the package metadata (name and version) inside the wheel. This validation ensures that wheels are correctly named and helps prevent installation of malformed packages.
+
+However, in some cases you may need to install wheels where the filename version doesn't match the metadata version. The `skip-wheel-filename-check` option allows you to disable this validation.
+
+!!! warning "One skip-wheel-filename-check per environment"
+    Only one `skip-wheel-filename-check` can be defined per environment or solve-group, otherwise, an error will be shown.
+
+#### Possible values:
+
+- **`false`** (default): Perform wheel filename validation. Installation will fail if filename and metadata don't match.
+- **`true`**: Skip wheel filename validation. Allow installing wheels with mismatched filename and metadata versions.
+
+#### Precedence
+
+The `UV_SKIP_WHEEL_FILENAME_CHECK` environment variable takes precedence over the `skip-wheel-filename-check` pypi-option. This allows for temporary overrides without modifying the manifest.
+
+
+Example:
+```toml
+[pypi-options]
+# Allow installing malformed wheels
+skip-wheel-filename-check = true 
+```
+
+Or set per feature:
+```toml
+[feature.special.pypi-options]
+# Only for this feature's environment
+skip-wheel-filename-check = true
+```
+
 ## 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.

src/assets/pixi/tutorials/ros2.md

@@ -181,7 +181,7 @@ hello = { cmd = "ros2 run my_package my_node", depends-on = ["build"] }
 To build a C++ node you need to add the `ament_cmake` and some other build dependencies to your manifest file.
 
 ```shell
-pixi add ros-humble-ament-cmake-auto compilers pkg-config cmake ninja
+pixi add ros-humble-ament-cmake-auto compilers pkg-config "cmake<4" ninja colcon-common-extensions
 ```
 
 Now you can create a C++ node with the following command

src/assets/pixi/workspace/advanced_tasks.md

@@ -31,6 +31,9 @@ set = "export VAR=hello && echo $VAR"
 copy = "cp pixi.toml pixi_backup.toml"
 clean = "rm pixi_backup.toml"
 move = "mv pixi.toml backup.toml"
+
+# Setting a default environment for the task
+test = { cmd = "pytest", default-environment = "test" }
 ```
 
 ## Depends on
@@ -157,6 +160,18 @@ This will add the following line to [manifest file](../reference/pixi_manifest.m
 bar = { cmd = "python bar.py", cwd = "scripts" }
 ```
 
+## Default environment
+
+You can set the default Pixi [environment](../tutorials/multi_environment.md#adding-an-environment) used by a task using the `default-environment` field:
+```toml title="pixi.toml"
+--8<-- "docs/source_files/pixi_tomls/task_default_environment.toml:default-environment"
+```
+
+The default environment can be overridden as usual with the `--environment` argument:
+```shell
+pixi run -e other_environment test
+```
+
 ## Task Arguments
 
 Tasks can accept arguments that can be referenced in the command. This provides more flexibility and reusability for your tasks.