Fix linting and tests

Author: thomasschafer

crates/uv/tests/it/show_settings.rs

@@ -7760,7 +7760,7 @@ fn preview_features() {
         show_settings: true,
         preview: Preview {
             flags: PreviewFeatures(
-                PYTHON_INSTALL_DEFAULT | PYTHON_UPGRADE | JSON_OUTPUT | PYLOCK | ADD_BOUNDS | PACKAGE_CONFLICTS | EXTRA_BUILD_DEPENDENCIES | DETECT_MODULE_CONFLICTS | FORMAT | NATIVE_AUTH | S3_ENDPOINT,
+                PYTHON_INSTALL_DEFAULT | PYTHON_UPGRADE | JSON_OUTPUT | PYLOCK | ADD_BOUNDS | PACKAGE_CONFLICTS | EXTRA_BUILD_DEPENDENCIES | DETECT_MODULE_CONFLICTS | FORMAT | NATIVE_AUTH | S3_ENDPOINT | SBOM_EXPORT,
             ),
         },
         python_preference: Managed,
@@ -7988,7 +7988,7 @@ fn preview_features() {
         show_settings: true,
         preview: Preview {
             flags: PreviewFeatures(
-                PYTHON_INSTALL_DEFAULT | PYTHON_UPGRADE | JSON_OUTPUT | PYLOCK | ADD_BOUNDS | PACKAGE_CONFLICTS | EXTRA_BUILD_DEPENDENCIES | DETECT_MODULE_CONFLICTS | FORMAT | NATIVE_AUTH | S3_ENDPOINT,
+                PYTHON_INSTALL_DEFAULT | PYTHON_UPGRADE | JSON_OUTPUT | PYLOCK | ADD_BOUNDS | PACKAGE_CONFLICTS | EXTRA_BUILD_DEPENDENCIES | DETECT_MODULE_CONFLICTS | FORMAT | NATIVE_AUTH | S3_ENDPOINT | SBOM_EXPORT,
             ),
         },
         python_preference: Managed,

docs/guides/export.md

@@ -5,7 +5,8 @@ description: Exporting a lockfile to different formats
 
 # Exporting a lockfile
 
-uv can export a lockfile to different formats for integration with other tools and workflows. The `uv export` command supports multiple output formats, each suited to different use cases.
+uv can export a lockfile to different formats for integration with other tools and workflows. The
+`uv export` command supports multiple output formats, each suited to different use cases.
 
 For more details on lockfiles and how they're created, see the
 [project layout](../concepts/projects/layout.md) and
@@ -15,9 +16,12 @@ For more details on lockfiles and how they're created, see the
 
 uv supports three export formats:
 
-- `requirements.txt`: The traditional pip-compatible [requirements file format](https://pip.pypa.io/en/stable/reference/requirements-file-format/).
-- `pylock.toml`: The standardized Python lockfile format defined in [PEP 751](https://peps.python.org/pep-0751/).
-- `CycloneDX`: An industry-standard [Software Bill of Materials (SBOM)](https://cyclonedx.org/) format.
+- `requirements.txt`: The traditional pip-compatible
+  [requirements file format](https://pip.pypa.io/en/stable/reference/requirements-file-format/).
+- `pylock.toml`: The standardized Python lockfile format defined in
+  [PEP 751](https://peps.python.org/pep-0751/).
+- `CycloneDX`: An industry-standard [Software Bill of Materials (SBOM)](https://cyclonedx.org/)
+  format.
 
 The format can be specified with the `--format` flag:
 
@@ -39,15 +43,17 @@ $ uv export --format cyclonedx1.5
 
 ## `requirements.txt` format
 
-The `requirements.txt` format is the most widely supported format for Python dependencies. It can be used with `pip` and other Python package managers.
+The `requirements.txt` format is the most widely supported format for Python dependencies. It can be
+used with `pip` and other Python package managers.
 
 ### Basic usage
 
 ```console
 $ uv export --format requirements.txt
 ```
 
-The generated `requirements.txt` file can then be installed via `uv pip install`, or with other tools like `pip`.
+The generated `requirements.txt` file can then be installed via `uv pip install`, or with other
+tools like `pip`.
 
 !!! note
 
@@ -58,7 +64,8 @@ The generated `requirements.txt` file can then be installed via `uv pip install`
 
 ## `pylock.toml` format
 
-[PEP 751](https://peps.python.org/pep-0751/) defines a TOML-based lockfile format for Python dependencies. uv can export your project's dependency lockfile to this format.
+[PEP 751](https://peps.python.org/pep-0751/) defines a TOML-based lockfile format for Python
+dependencies. uv can export your project's dependency lockfile to this format.
 
 ### Basic usage
 
@@ -68,15 +75,19 @@ $ uv export --format pylock.toml
 
 ## CycloneDX SBOM format
 
-uv can export your project's dependency lockfile as a Software Bill of Materials (SBOM) in CycloneDX format. SBOMs provide a comprehensive inventory of all software components in your application, which is useful for security auditing, compliance, and supply chain transparency.
+uv can export your project's dependency lockfile as a Software Bill of Materials (SBOM) in CycloneDX
+format. SBOMs provide a comprehensive inventory of all software components in your application,
+which is useful for security auditing, compliance, and supply chain transparency.
 
 !!! important
 
     Support for exporting to CycloneDX is in [preview](../concepts/preview.md), so may be subject to change.
 
 ### What is CycloneDX?
 
-[CycloneDX](https://cyclonedx.org/) is an industry-standard format for creating Software Bill of Materials. CycloneDX is machine readable and widely supported by security scanning tools, vulnerability databases, and Software Composition Analysis (SCA) platforms.
+[CycloneDX](https://cyclonedx.org/) is an industry-standard format for creating Software Bill of
+Materials. CycloneDX is machine readable and widely supported by security scanning tools,
+vulnerability databases, and Software Composition Analysis (SCA) platforms.
 
 ### Basic usage
 
@@ -86,11 +97,14 @@ To export your project's lockfile as a CycloneDX SBOM:
 $ uv export --format cyclonedx1.5
 ```
 
-This will generate a JSON-encoded CycloneDX v1.5 document containing your project and all of its dependencies.
+This will generate a JSON-encoded CycloneDX v1.5 document containing your project and all of its
+dependencies.
 
 ### SBOM Structure
 
-The generated SBOM follows the [CycloneDX specification](https://cyclonedx.org/specification/overview/). uv also includes the following custom properties on components:
+The generated SBOM follows the
+[CycloneDX specification](https://cyclonedx.org/specification/overview/). uv also includes the
+following custom properties on components:
 
 - `uv:package:marker`: Environment markers (e.g., `python_version >= "3.8"`)
 - `uv:workspace:path`: Relative path for workspace members