[System]
You are a helpful assistant that answers strictly in JSON. Here's the JSON schema you must adhere to:
<schema>
{"$schema":"http://json-schema.org/draft-07/schema#","$id":"https://json.schemastore.org/uv.json","title":"CombinedOptions","description":"Metadata and configuration for uv.","type":"object","properties":{"allow-insecure-host":{"description":"Allow insecure connections to host.\n\nExpects to receive either a hostname (e.g., `localhost`), a host-port pair (e.g., `localhost:8080`), or a URL (e.g., `https://localhost`).\n\nWARNING: Hosts included in this list will not be verified against the system's certificate store. Only use `--allow-insecure-host` in a secure network with verified sources, as it bypasses SSL verification and could expose you to MITM attacks.","type":["array","null"],"items":{"$ref":"#/definitions/TrustedHost"}},"cache-dir":{"description":"Path to the cache directory.\n\nDefaults to `$HOME/Library/Caches/uv` on macOS, `$XDG_CACHE_HOME/uv` or `$HOME/.cache/uv` on Linux, and `%LOCALAPPDATA%\\uv\\cache` on Windows.","type":["string","null"]},"cache-keys":{"description":"The keys to consider when caching builds for the project.\n\nCache keys enable you to specify the files or directories that should trigger a rebuild when modified. By default, uv will rebuild a project whenever the `pyproject.toml`, `setup.py`, or `setup.cfg` files in the project directory are modified, i.e.:\n\n```toml cache-keys = [{ file = \"pyproject.toml\" }, { file = \"setup.py\" }, { file = \"setup.cfg\" }] ```\n\nAs an example: if a project uses dynamic metadata to read its dependencies from a `requirements.txt` file, you can specify `cache-keys = [{ file = \"requirements.txt\" }, { file = \"pyproject.toml\" }]` to ensure that the project is rebuilt whenever the `requirements.txt` file is modified (in addition to watching the `pyproject.toml`).\n\nGlobs are supported, following the syntax of the [`glob`](https://docs.rs/glob/0.3.1/glob/struct.Pattern.html) crate. For example, to invalidate the cache whenever a `.toml` file in the project directory or any of its subdirectories is modified, you can specify `cache-keys = [{ file = \"**/*.toml\" }]`. Note that the use of globs can be expensive, as uv may need to walk the filesystem to determine whether any files have changed.\n\nCache keys can also include version control information. For example, if a project uses `setuptools_scm` to read its version from a Git commit, you can specify `cache-keys = [{ git = { commit = true }, { file = \"pyproject.toml\" }]` to include the current Git commit hash in the cache key (in addition to the `pyproject.toml`). Git tags are also supported via `cache-keys = [{ git = { commit = true, tags = true } }]`.\n\nCache keys can also include environment variables. For example, if a project relies on `MACOSX_DEPLOYMENT_TARGET` or other environment variables to determine its behavior, you can specify `cache-keys = [{ env = \"MACOSX_DEPLOYMENT_TARGET\" }]` to invalidate the cache whenever the environment variable changes.\n\nCache keys only affect the project defined by the `pyproject.toml` in which they're specified (as opposed to, e.g., affecting all members in a workspace), and all paths and globs are interpreted as relative to the project directory.","type":["array","null"],"items":{"$ref":"#/definitions/CacheKey"}},"check-url":{"description":"Check an index URL for existing files to skip duplicate uploads.\n\nThis option allows retrying publishing that failed after only some, but not all files have been uploaded, and handles error due to parallel uploads of the same file.\n\nBefore uploading, the index is checked. If the exact same file already exists in the index, the file will not be uploaded. If an error occurred during the upload, the index is checked again, to handle cases where the identical file was uploaded twice in parallel.\n\nThe exact behavior will vary based on the index. When uploading to PyPI, uploading the same file succeeds even without `--check-url`, while most other indexes error.\n\nThe index must provide one of the supported hashes (SHA-256, SHA-384, or SHA-512).","anyOf":[{"$ref":"#/definitions/IndexUrl"},{"type":"null"}]},"compile-bytecode":{"description":"Compile Python files to bytecode after installation.\n\nBy default, uv does not compile Python (`.py`) files to bytecode (`__pycache__/*.pyc`); instead, compilation is performed lazily the first time a module is imported. For use-cases in which start time is critical, such as CLI applications and Docker containers, this option can be enabled to trade longer installation times for faster start times.\n\nWhen enabled, uv will process the entire site-packages directory (including packages that are not being modified by the current operation) for consistency. Like pip, it will also ignore errors.","type":["boolean","null"]},"concurrent-builds":{"description":"The maximum number of source distributions that uv will build concurrently at any given time.\n\nDefaults to the number of available CPU cores.","type":["integer","null"],"format":"uint","minimum":1.0},"concurrent-downloads":{"description":"The maximum number of in-flight concurrent downloads that uv will perform at any given time.","type":["integer","null"],"format":"uint","minimum":1.0},"concurrent-installs":{"description":"The number of threads used when installing and unzipping packages.\n\nDefaults to the number of available CPU cores.","type":["integer","null"],"format":"uint","minimum":1.0},"config-settings":{"description":"Settings to pass to the [PEP 517](https://peps.python.org/pep-0517/) build backend, specified as `KEY=VALUE` pairs.","anyOf":[{"$ref":"#/definitions/ConfigSettings"},{"type":"null"}]},"conflicts":{"description":"A list of sets of conflicting groups or extras.","anyOf":[{"$ref":"#/definitions/SchemaConflicts"},{"type":"null"}]},"constraint-dependencies":{"description":"PEP 508-style requirements, e.g., `ruff==0.5.0`, or `ruff @ https://...`.","type":["array","null"],"items":{"type":"string"}},"default-groups":{"description":"The list of `dependency-groups` to install by default.","anyOf":[{"type":"array","items":{"$ref":"#/definitions/GroupName"}},{"type":"string","const":"all"},{"type":"null"}]},"dependency-metadata":{"description":"Pre-defined static metadata for dependencies of the project (direct or transitive). When provided, enables the resolver to use the specified metadata instead of querying the registry or building the relevant package from source.\n\nMetadata should be provided in adherence with the [Metadata 2.3](https://packaging.python.org/en/latest/specifications/core-metadata/) standard, though only the following fields are respected:\n\n- `name`: The name of the package. - (Optional) `version`: The version of the package. If omitted, the metadata will be applied to all versions of the package. - (Optional) `requires-dist`: The dependencies of the package (e.g., `werkzeug>=0.14`). - (Optional) `requires-python`: The Python version required by the package (e.g., `>=3.10`). - (Optional) `provides-extras`: The extras provided by the package.","type":["array","null"],"items":{"$ref":"#/definitions/StaticMetadata"}},"dev-dependencies":{"description":"PEP 508-style requirements, e.g., `ruff==0.5.0`, or `ruff @ https://...`.","type":["array","null"],"items":{"type":"string"}},"environments":{"description":"A list of environment markers, e.g., `python_version >= '3.6'`.","type":["array","null"],"items":{"type":"string"}},"exclude-newer":{"description":"Limit candidate packages to those that were uploaded prior to the given date.\n\nAccepts both [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339.html) timestamps (e.g., `2006-12-02T02:07:43Z`) and local dates in the same format (e.g., `2006-12-02`) in your system's configured time zone.","anyOf":[{"$ref":"#/definitions/ExcludeNewer"},{"type":"null"}]},"extra-index-url":{"description":"Extra URLs of package indexes to use, in addition to `--index-url`.\n\nAccepts either a repository compliant with [PEP 503](https://peps.python.org/pep-0503/) (the simple repository API), or a local directory laid out in the same format.\n\nAll indexes provided via this flag take priority over the index specified by [`index_url`](#index-url) or [`index`](#index) with `default = true`. When multiple indexes are provided, earlier values take priority.\n\nTo control uv's resolution strategy when multiple indexes are present, see [`index_strategy`](#index-strategy).\n\n(Deprecated: use `index` instead.)","type":["array","null"],"items":{"$ref":"#/definitions/IndexUrl"}},"find-links":{"description":"Locations to search for candidate distributions, in addition to those found in the registry indexes.\n\nIf a path, the target must be a directory that contains packages as wheel files (`.whl`) or source distributions (e.g., `.tar.gz` or `.zip`) at the top level.\n\nIf a URL, the page must contain a flat list of links to package files adhering to the formats described above.","type":["array","null"],"items":{"$ref":"#/definitions/IndexUrl"}},"fork-strategy":{"description":"The strategy to use when selecting multiple versions of a given package across Python versions and platforms.\n\nBy default, uv will optimize for selecting the latest version of each package for each supported Python version (`requires-python`), while minimizing the number of selected versions across platforms.\n\nUnder `fewest`, uv will minimize the number of selected versions for each package, preferring older versions that are compatible with a wider range of supported Python versions or platforms.","anyOf":[{"$ref":"#/definitions/ForkStrategy"},{"type":"null"}]},"index":{"description":"The indexes to use when resolving dependencies.\n\nAccepts either a repository compliant with [PEP 503](https://peps.python.org/pep-0503/) (the simple repository API), or a local directory laid out in the same format.\n\nIndexes are considered in the order in which they're defined, such that the first-defined index has the highest priority. Further, the indexes provided by this setting are given higher priority than any indexes specified via [`index_url`](#index-url) or [`extra_index_url`](#extra-index-url). uv will only consider the first index that contains a given package, unless an alternative [index strategy](#index-strategy) is specified.\n\nIf an index is marked as `explicit = true`, it will be used exclusively for the dependencies that select it explicitly via `[tool.uv.sources]`, as in:\n\n```toml [[tool.uv.index]] name = \"pytorch\" url = \"https://download.pytorch.org/whl/cu121\" explicit = true\n\n[tool.uv.sources] torch = { index = \"pytorch\" } ```\n\nIf an index is marked as `default = true`, it will be moved to the end of the prioritized list, such that it is given the lowest priority when resolving packages. Additionally, marking an index as default will disable the PyPI default index.","type":["array","null"],"items":{"$ref":"#/definitions/Index"}},"index-strategy":{"description":"The strategy to use when resolving against multiple index URLs.\n\nBy default, uv will stop at the first index on which a given package is available, and limit resolutions to those present on that first index (`first-index`). This prevents \"dependency confusion\" attacks, whereby an attacker can upload a malicious package under the same name to an alternate index.","anyOf":[{"$ref":"#/definitions/IndexStrategy"},{"type":"null"}]},"index-url":{"description":"The URL of the Python package index (by default: <https://pypi.org/simple>).\n\nAccepts either a repository compliant with [PEP 503](https://peps.python.org/pep-0503/) (the simple repository API), or a local directory laid out in the same format.\n\nThe index provided by this setting is given lower priority than any indexes specified via [`extra_index_url`](#extra-index-url) or [`index`](#index).\n\n(Deprecated: use `index` instead.)","anyOf":[{"$ref":"#/definitions/IndexUrl"},{"type":"null"}]},"keyring-provider":{"description":"Attempt to use `keyring` for authentication for index URLs.\n\nAt present, only `--keyring-provider subprocess` is supported, which configures uv to use the `keyring` CLI to handle authentication.","anyOf":[{"$ref":"#/definitions/KeyringProviderType"},{"type":"null"}]},"link-mode":{"description":"The method to use when installing packages from the global cache.\n\nDefaults to `clone` (also known as Copy-on-Write) on macOS, and `hardlink` on Linux and Windows.","anyOf":[{"$ref":"#/definitions/LinkMode"},{"type":"null"}]},"managed":{"description":"Whether the project is managed by uv. If `false`, uv will ignore the project when `uv run` is invoked.","type":["boolean","null"]},"native-tls":{"description":"Whether to load TLS certificates from the platform's native certificate store.\n\nBy default, uv loads certificates from the bundled `webpki-roots` crate. The `webpki-roots` are a reliable set of trust roots from Mozilla, and including them in uv improves portability and performance (especially on macOS).\n\nHowever, in some cases, you may want to use the platform's native certificate store, especially if you're relying on a corporate trust root (e.g., for a mandatory proxy) that's included in your system's certificate store.","type":["boolean","null"]},"no-binary":{"description":"Don't install pre-built wheels.\n\nThe given packages will be built and installed from source. The resolver will still use pre-built wheels to extract package metadata, if available.","type":["boolean","null"]},"no-binary-package":{"description":"Don't install pre-built wheels for a specific package.","type":["array","null"],"items":{"$ref":"#/definitions/PackageName"}},"no-build":{"description":"Don't build source distributions.\n\nWhen enabled, resolving will not run arbitrary Python code. The cached wheels of already-built source distributions will be reused, but operations that require building distributions will exit with an error.","type":["boolean","null"]},"no-build-isolation":{"description":"Disable isolation when building source distributions.\n\nAssumes that build dependencies specified by [PEP 518](https://peps.python.org/pep-0518/) are already installed.","type":["boolean","null"]},"no-build-isolation-package":{"description":"Disable isolation when building source distributions for a specific package.\n\nAssumes that the packages' build dependencies specified by [PEP 518](https://peps.python.org/pep-0518/) are already installed.","type":["array","null"],"items":{"$ref":"#/definitions/PackageName"}},"no-build-package":{"description":"Don't build source distributions for a specific package.","type":["array","null"],"items":{"$ref":"#/definitions/PackageName"}},"no-cache":{"description":"Avoid reading from or writing to the cache, instead using a temporary directory for the duration of the operation.","type":["boolean","null"]},"no-index":{"description":"Ignore all registry indexes (e.g., PyPI), instead relying on direct URL dependencies and those provided via `--find-links`.","type":["boolean","null"]},"no-sources":{"description":"Ignore the `tool.uv.sources` table when resolving dependencies. Used to lock against the standards-compliant, publishable package metadata, as opposed to using any local or Git sources.","type":["boolean","null"]},"offline":{"description":"Disable network access, relying only on locally cached data and locally available files.","type":["boolean","null"]},"override-dependencies":{"description":"PEP 508-style requirements, e.g., `ruff==0.5.0`, or `ruff @ https://...`.","type":["array","null"],"items":{"type":"string"}},"package":{"description":"Whether the project should be considered a Python package, or a non-package (\"virtual\") project.\n\nPackages are built and installed into the virtual environment in editable mode and thus require a build backend, while virtual projects are _not_ built or installed; instead, only their dependencies are included in the virtual environment.\n\nCreating a package requires that a `build-system` is present in the `pyproject.toml`, and that the project adheres to a structure that adheres to the build backend's expectations (e.g., a `src` layout).","type":["boolean","null"]},"pip":{"anyOf":[{"$ref":"#/definitions/PipOptions"},{"type":"null"}]},"prerelease":{"description":"The strategy to use when considering pre-release versions.\n\nBy default, uv will accept pre-releases for packages that _only_ publish pre-releases, along with first-party requirements that contain an explicit pre-release marker in the declared specifiers (`if-necessary-or-explicit`).","anyOf":[{"$ref":"#/definitions/PrereleaseMode"},{"type":"null"}]},"preview":{"description":"Whether to enable experimental, preview features.","type":["boolean","null"]},"publish-url":{"description":"The URL for publishing packages to the Python package index (by default: <https://upload.pypi.org/legacy/>).","type":["string","null"],"format":"uri"},"pypy-install-mirror":{"description":"Mirror URL to use for downloading managed PyPy installations.\n\nBy default, managed PyPy installations are downloaded from [downloads.python.org](https://downloads.python.org/). This variable can be set to a mirror URL to use a different source for PyPy installations. The provided URL will replace `https://downloads.python.org/pypy` in, e.g., `https://downloads.python.org/pypy/pypy3.8-v7.3.7-osx64.tar.bz2`.\n\nDistributions can be read from a local directory by using the `file://` URL scheme.","type":["string","null"]},"python-downloads":{"description":"Whether to allow Python downloads.","anyOf":[{"$ref":"#/definitions/PythonDownloads"},{"type":"null"}]},"python-install-mirror":{"description":"Mirror URL for downloading managed Python installations.\n\nBy default, managed Python installations are downloaded from [`python-build-standalone`](https://github.com/astral-sh/python-build-standalone). This variable can be set to a mirror URL to use a different source for Python installations. The provided URL will replace `https://github.com/astral-sh/python-build-standalone/releases/download` in, e.g., `https://github.com/astral-sh/python-build-standalone/releases/download/20240713/cpython-3.12.4%2B20240713-aarch64-apple-darwin-install_only.tar.gz`.\n\nDistributions can be read from a local directory by using the `file://` URL scheme.","type":["string","null"]},"python-preference":{"description":"Whether to prefer using Python installations that are already present on the system, or those that are downloaded and installed by uv.","anyOf":[{"$ref":"#/definitions/PythonPreference"},{"type":"null"}]},"reinstall":{"description":"Reinstall all packages, regardless of whether they're already installed. Implies `refresh`.","type":["boolean","null"]},"reinstall-package":{"description":"Reinstall a specific package, regardless of whether it's already installed. Implies `refresh-package`.","type":["array","null"],"items":{"$ref":"#/definitions/PackageName"}},"required-version":{"description":"Enforce a requirement on the version of uv.\n\nIf the version of uv does not meet the requirement at runtime, uv will exit with an error.\n\nAccepts a [PEP 440](https://peps.python.org/pep-0440/) specifier, like `==0.5.0` or `>=0.5.0`.","anyOf":[{"$ref":"#/definitions/RequiredVersion"},{"type":"null"}]},"resolution":{"description":"The strategy to use when selecting between the different compatible versions for a given package requirement.\n\nBy default, uv will use the latest compatible version of each package (`highest`).","anyOf":[{"$ref":"#/definitions/ResolutionMode"},{"type":"null"}]},"sources":{"description":"The sources to use when resolving dependencies.\n\n`tool.uv.sources` enriches the dependency metadata with additional sources, incorporated during development. A dependency source can be a Git repository, a URL, a local path, or an alternative registry.\n\nSee [Dependencies](https://docs.astral.sh/uv/concepts/projects/dependencies/) for more.","anyOf":[{"$ref":"#/definitions/ToolUvSources"},{"type":"null"}]},"trusted-publishing":{"description":"Configure trusted publishing via GitHub Actions.\n\nBy default, uv checks for trusted publishing when running in GitHub Actions, but ignores it if it isn't configured or the workflow doesn't have enough permissions (e.g., a pull request from a fork).","anyOf":[{"$ref":"#/definitions/TrustedPublishing"},{"type":"null"}]},"upgrade":{"description":"Allow package upgrades, ignoring pinned versions in any existing output file.","type":["boolean","null"]},"upgrade-package":{"description":"Allow upgrades for a specific package, ignoring pinned versions in any existing output file.\n\nAccepts both standalone package names (`ruff`) and version specifiers (`ruff<0.5.0`).","type":["array","null"],"items":{"$ref":"#/definitions/Requirement"}},"workspace":{"description":"The workspace definition for the project, if any.","anyOf":[{"$ref":"#/definitions/ToolUvWorkspace"},{"type":"null"}]}},"definitions":{"AnnotationStyle":{"description":"Indicate the style of annotation comments, used to indicate the dependencies that requested each package.","oneOf":[{"description":"Render the annotations on a single, comma-separated line.","type":"string","enum":["line"]},{"description":"Render each annotation on its own line.","type":"string","enum":["split"]}]},"CacheKey":{"anyOf":[{"description":"Ex) `\"Cargo.lock\"` or `\"**/*.toml\"`","type":"string"},{"description":"Ex) `{ file = \"Cargo.lock\" }` or `{ file = \"**/*.toml\" }`","type":"object","required":["file"],"properties":{"file":{"type":"string"}},"additionalProperties":false},{"description":"Ex) `{ git = true }` or `{ git = { commit = true, tags = false } }`","type":"object","required":["git"],"properties":{"git":{"$ref":"#/definitions/GitPattern"}},"additionalProperties":false},{"description":"Ex) `{ env = \"UV_CACHE_INFO\" }`","type":"object","required":["env"],"properties":{"env":{"type":"string"}},"additionalProperties":false}]},"ConfigSettingValue":{"oneOf":[{"description":"The value consists of a single string.","type":"string"},{"description":"The value consists of a list of strings.","type":"array","items":{"type":"string"}}]},"ConfigSettings":{"description":"Settings to pass to a PEP 517 build backend, structured as a map from (string) key to string or list of strings.\n\nSee: <https://peps.python.org/pep-0517/#config-settings>","type":"object","additionalProperties":{"$ref":"#/definitions/ConfigSettingValue"}},"ExcludeNewer":{"description":"Exclude distributions uploaded after the given timestamp.\n\nAccepts both RFC 3339 timestamps (e.g., `2006-12-02T02:07:43Z`) and local dates in the same format (e.g., `2006-12-02`).","type":"string","pattern":"^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}:\\d{2}(Z|[+-]\\d{2}:\\d{2}))?$"},"ExtraName":{"description":"The normalized name of an extra dependency.\n\nConverts the name to lowercase and collapses runs of `-`, `_`, and `.` down to a single `-`. For example, `---`, `.`, and `__` are all converted to a single `-`.\n\nSee: - <https://peps.python.org/pep-0685/#specification/> - <https://packaging.python.org/en/latest/specifications/name-normalization/>","type":"string"},"ForkStrategy":{"oneOf":[{"description":"Optimize for selecting the fewest number of versions for each package. Older versions may be preferred if they are compatible with a wider range of supported Python versions or platforms.","type":"string","enum":["fewest"]},{"description":"Optimize for selecting latest supported version of each package, for each supported Python version.","type":"string","enum":["requires-python"]}]},"GitPattern":{"anyOf":[{"type":"boolean"},{"$ref":"#/definitions/GitSet"}]},"GitSet":{"type":"object","properties":{"commit":{"type":["boolean","null"]},"tags":{"type":["boolean","null"]}},"additionalProperties":false},"GroupName":{"description":"The normalized name of a dependency group.\n\nSee: - <https://peps.python.org/pep-0735/> - <https://packaging.python.org/en/latest/specifications/name-normalization/>","type":"string"},"Index":{"type":"object","required":["url"],"properties":{"default":{"description":"Mark the index as the default index.\n\nBy default, uv uses PyPI as the default index, such that even if additional indexes are defined via `[[tool.uv.index]]`, PyPI will still be used as a fallback for packages that aren't found elsewhere. To disable the PyPI default, set `default = true` on at least one other index.\n\nMarking an index as default will move it to the front of the list of indexes, such that it is given the highest priority when resolving packages.","default":false,"type":"boolean"},"explicit":{"description":"Mark the index as explicit.\n\nExplicit indexes will _only_ be used when explicitly requested via a `[tool.uv.sources]` definition, as in:\n\n```toml [[tool.uv.index]] name = \"pytorch\" url = \"https://download.pytorch.org/whl/cu121\" explicit = true\n\n[tool.uv.sources] torch = { index = \"pytorch\" } ```","default":false,"type":"boolean"},"name":{"description":"The name of the index.\n\nIndex names can be used to reference indexes elsewhere in the configuration. For example, you can pin a package to a specific index by name:\n\n```toml [[tool.uv.index]] name = \"pytorch\" url = \"https://download.pytorch.org/whl/cu121\"\n\n[tool.uv.sources] torch = { index = \"pytorch\" } ```","anyOf":[{"$ref":"#/definitions/IndexName"},{"type":"null"}]},"publish-url":{"description":"The URL of the upload endpoint.\n\nWhen using `uv publish --index <name>`, this URL is used for publishing.\n\nA configuration for the default index PyPI would look as follows:\n\n```toml [[tool.uv.index]] name = \"pypi\" url = \"https://pypi.org/simple\" publish-url = \"https://upload.pypi.org/legacy/\" ```","type":["string","null"],"format":"uri"},"url":{"description":"The URL of the index.\n\nExpects to receive a URL (e.g., `https://pypi.org/simple`) or a local path.","allOf":[{"$ref":"#/definitions/IndexUrl"}]}}},"IndexName":{"description":"The normalized name of an index.\n\nIndex names may contain letters, digits, hyphens, underscores, and periods, and must be ASCII.","type":"string"},"IndexStrategy":{"oneOf":[{"description":"Only use results from the first index that returns a match for a given package name.\n\nWhile this differs from pip's behavior, it's the default index strategy as it's the most secure.","type":"string","enum":["first-index"]},{"description":"Search for every package name across all indexes, exhausting the versions from the first index before moving on to the next.\n\nIn this strategy, we look for every package across all indexes. When resolving, we attempt to use versions from the indexes in order, such that we exhaust all available versions from the first index before moving on to the next. Further, if a version is found to be incompatible in the first index, we do not reconsider that version in subsequent indexes, even if the secondary index might contain compatible versions (e.g., variants of the same versions with different ABI tags or Python version constraints).\n\nSee: <https://peps.python.org/pep-0708/>","type":"string","enum":["unsafe-first-match"]},{"description":"Search for every package name across all indexes, preferring the \"best\" version found. If a package version is in multiple indexes, only look at the entry for the first index.\n\nIn this strategy, we look for every package across all indexes. When resolving, we consider all versions from all indexes, choosing the \"best\" version found (typically, the highest compatible version).\n\nThis most closely matches pip's behavior, but exposes the resolver to \"dependency confusion\" attacks whereby malicious actors can publish packages to public indexes with the same name as internal packages, causing the resolver to install the malicious package in lieu of the intended internal package.\n\nSee: <https://peps.python.org/pep-0708/>","type":"string","enum":["unsafe-best-match"]}]},"IndexUrl":{"description":"The URL of an index to use for fetching packages (e.g., `https://pypi.org/simple`).","type":"string"},"KeyringProviderType":{"description":"Keyring provider type to use for credential lookup.","oneOf":[{"description":"Do not use keyring for credential lookup.","type":"string","enum":["disabled"]},{"description":"Use the `keyring` command for credential lookup.","type":"string","enum":["subprocess"]}]},"LinkMode":{"oneOf":[{"description":"Clone (i.e., copy-on-write) packages from the wheel into the `site-packages` directory.","type":"string","enum":["clone"]},{"description":"Copy packages from the wheel into the `site-packages` directory.","type":"string","enum":["copy"]},{"description":"Hard link packages from the wheel into the `site-packages` directory.","type":"string","enum":["hardlink"]},{"description":"Symbolically link packages from the wheel into the `site-packages` directory.\n\nWARNING: The use of symlinks is discouraged, as they create tight coupling between the cache and the target environment. For example, clearing the cache (`uv cache clear`) will break all installed packages by way of removing the underlying source files. Use symlinks with caution.","type":"string","enum":["symlink"]}]},"MarkerTree":{"description":"A PEP 508-compliant marker expression, e.g., `sys_platform == 'Darwin'`","type":"string"},"PackageName":{"description":"The normalized name of a package.\n\nConverts the name to lowercase and collapses runs of `-`, `_`, and `.` down to a single `-`. For example, `---`, `.`, and `__` are all converted to a single `-`.\n\nSee: <https://packaging.python.org/en/latest/specifications/name-normalization/>","type":"string"},"PackageNameSpecifier":{"description":"The name of a package, or `:all:` or `:none:` to select or omit all packages, respectively.","type":"string","pattern":"^(:none:|:all:|([a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9._-]*[a-zA-Z0-9]))$"},"PipOptions":{"description":"Settings that are specific to the `uv pip` command-line interface.\n\nThese values will be ignored when running commands outside the `uv pip` namespace (e.g., `uv lock`, `uvx`).","type":"object","properties":{"all-extras":{"description":"Include all optional dependencies.\n\nOnly applies to `pyproject.toml`, `setup.py`, and `setup.cfg` sources.","type":["boolean","null"]},"allow-empty-requirements":{"description":"Allow `uv pip sync` with empty requirements, which will clear the environment of all packages.","type":["boolean","null"]},"annotation-style":{"description":"The style of the annotation comments included in the output file, used to indicate the source of each package.","anyOf":[{"$ref":"#/definitions/AnnotationStyle"},{"type":"null"}]},"break-system-packages":{"description":"Allow uv to modify an `EXTERNALLY-MANAGED` Python installation.\n\nWARNING: `--break-system-packages` is intended for use in continuous integration (CI) environments, when installing into Python installations that are managed by an external package manager, like `apt`. It should be used with caution, as such Python installations explicitly recommend against modifications by other package managers (like uv or pip).","type":["boolean","null"]},"compile-bytecode":{"description":"Compile Python files to bytecode after installation.\n\nBy default, uv does not compile Python (`.py`) files to bytecode (`__pycache__/*.pyc`); instead, compilation is performed lazily the first time a module is imported. For use-cases in which start time is critical, such as CLI applications and Docker containers, this option can be enabled to trade longer installation times for faster start times.\n\nWhen enabled, uv will process the entire site-packages directory (including packages that are not being modified by the current operation) for consistency. Like pip, it will also ignore errors.","type":["boolean","null"]},"config-settings":{"description":"Settings to pass to the [PEP 517](https://peps.python.org/pep-0517/) build backend, specified as `KEY=VALUE` pairs.","anyOf":[{"$ref":"#/definitions/ConfigSettings"},{"type":"null"}]},"custom-compile-command":{"description":"The header comment to include at the top of the output file generated by `uv pip compile`.\n\nUsed to reflect custom build scripts and commands that wrap `uv pip compile`.","type":["string","null"]},"dependency-metadata":{"description":"Pre-defined static metadata for dependencies of the project (direct or transitive). When provided, enables the resolver to use the specified metadata instead of querying the registry or building the relevant package from source.\n\nMetadata should be provided in adherence with the [Metadata 2.3](https://packaging.python.org/en/latest/specifications/core-metadata/) standard, though only the following fields are respected:\n\n- `name`: The name of the package. - (Optional) `version`: The version of the package. If omitted, the metadata will be applied to all versions of the package. - (Optional) `requires-dist`: The dependencies of the package (e.g., `werkzeug>=0.14`). - (Optional) `requires-python`: The Python version required by the package (e.g., `>=3.10`). - (Optional) `provides-extras`: The extras provided by the package.","type":["array","null"],"items":{"$ref":"#/definitions/StaticMetadata"}},"emit-build-options":{"description":"Include `--no-binary` and `--only-binary` entries in the output file generated by `uv pip compile`.","type":["boolean","null"]},"emit-find-links":{"description":"Include `--find-links` entries in the output file generated by `uv pip compile`.","type":["boolean","null"]},"emit-index-annotation":{"description":"Include comment annotations indicating the index used to resolve each package (e.g., `# from https://pypi.org/simple`).","type":["boolean","null"]},"emit-index-url":{"description":"Include `--index-url` and `--extra-index-url` entries in the output file generated by `uv pip compile`.","type":["boolean","null"]},"emit-marker-expression":{"description":"Whether to emit a marker string indicating the conditions under which the set of pinned dependencies is valid.\n\nThe pinned dependencies may be valid even when the marker expression is false, but when the expression is true, the requirements are known to be correct.","type":["boolean","null"]},"exclude-newer":{"description":"Limit candidate packages to those that were uploaded prior to a given point in time.\n\nAccepts a superset of [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339.html) (e.g., `2006-12-02T02:07:43Z`). A full timestamp is required to ensure that the resolver will behave consistently across timezones.","anyOf":[{"$ref":"#/definitions/ExcludeNewer"},{"type":"null"}]},"extra":{"description":"Include optional dependencies from the specified extra; may be provided more than once.\n\nOnly applies to `pyproject.toml`, `setup.py`, and `setup.cfg` sources.","type":["array","null"],"items":{"$ref":"#/definitions/ExtraName"}},"extra-index-url":{"description":"Extra URLs of package indexes to use, in addition to `--index-url`.\n\nAccepts either a repository compliant with [PEP 503](https://peps.python.org/pep-0503/) (the simple repository API), or a local directory laid out in the same format.\n\nAll indexes provided via this flag take priority over the index specified by [`index_url`](#index-url). When multiple indexes are provided, earlier values take priority.\n\nTo control uv's resolution strategy when multiple indexes are present, see [`index_strategy`](#index-strategy).","type":["array","null"],"items":{"$ref":"#/definitions/IndexUrl"}},"find-links":{"description":"Locations to search for candidate distributions, in addition to those found in the registry indexes.\n\nIf a path, the target must be a directory that contains packages as wheel files (`.whl`) or source distributions (e.g., `.tar.gz` or `.zip`) at the top level.\n\nIf a URL, the page must contain a flat list of links to package files adhering to the formats described above.","type":["array","null"],"items":{"$ref":"#/definitions/IndexUrl"}},"fork-strategy":{"description":"The strategy to use when selecting multiple versions of a given package across Python versions and platforms.\n\nBy default, uv will optimize for selecting the latest version of each package for each supported Python version (`requires-python`), while minimizing the number of selected versions across platforms.\n\nUnder `fewest`, uv will minimize the number of selected versions for each package, preferring older versions that are compatible with a wider range of supported Python versions or platforms.","anyOf":[{"$ref":"#/definitions/ForkStrategy"},{"type":"null"}]},"generate-hashes":{"description":"Include distribution hashes in the output file.","type":["boolean","null"]},"index-strategy":{"description":"The strategy to use when resolving against multiple index URLs.\n\nBy default, uv will stop at the first index on which a given package is available, and limit resolutions to those present on that first index (`first-index`). This prevents \"dependency confusion\" attacks, whereby an attacker can upload a malicious package under the same name to an alternate index.","anyOf":[{"$ref":"#/definitions/IndexStrategy"},{"type":"null"}]},"index-url":{"description":"The URL of the Python package index (by default: <https://pypi.org/simple>).\n\nAccepts either a repository compliant with [PEP 503](https://peps.python.org/pep-0503/) (the simple repository API), or a local directory laid out in the same format.\n\nThe index provided by this setting is given lower priority than any indexes specified via [`extra_index_url`](#extra-index-url).","anyOf":[{"$ref":"#/definitions/IndexUrl"},{"type":"null"}]},"keyring-provider":{"description":"Attempt to use `keyring` for authentication for index URLs.\n\nAt present, only `--keyring-provider subprocess` is supported, which configures uv to use the `keyring` CLI to handle authentication.","anyOf":[{"$ref":"#/definitions/KeyringProviderType"},{"type":"null"}]},"link-mode":{"description":"The method to use when installing packages from the global cache.\n\nDefaults to `clone` (also known as Copy-on-Write) on macOS, and `hardlink` on Linux and Windows.","anyOf":[{"$ref":"#/definitions/LinkMode"},{"type":"null"}]},"no-annotate":{"description":"Exclude comment annotations indicating the source of each package from the output file generated by `uv pip compile`.","type":["boolean","null"]},"no-binary":{"description":"Don't install pre-built wheels.\n\nThe given packages will be built and installed from source. The resolver will still use pre-built wheels to extract package metadata, if available.\n\nMultiple packages may be provided. Disable binaries for all packages with `:all:`. Clear previously specified packages with `:none:`.","type":["array","null"],"items":{"$ref":"#/definitions/PackageNameSpecifier"}},"no-build":{"description":"Don't build source distributions.\n\nWhen enabled, resolving will not run arbitrary Python code. The cached wheels of already-built source distributions will be reused, but operations that require building distributions will exit with an error.\n\nAlias for `--only-binary :all:`.","type":["boolean","null"]},"no-build-isolation":{"description":"Disable isolation when building source distributions.\n\nAssumes that build dependencies specified by [PEP 518](https://peps.python.org/pep-0518/) are already installed.","type":["boolean","null"]},"no-build-isolation-package":{"description":"Disable isolation when building source distributions for a specific package.\n\nAssumes that the packages' build dependencies specified by [PEP 518](https://peps.python.org/pep-0518/) are already installed.","type":["array","null"],"items":{"$ref":"#/definitions/PackageName"}},"no-deps":{"description":"Ignore package dependencies, instead only add those packages explicitly listed on the command line to the resulting requirements file.","type":["boolean","null"]},"no-emit-package":{"description":"Specify a package to omit from the output resolution. Its dependencies will still be included in the resolution. Equivalent to pip-compile's `--unsafe-package` option.","type":["array","null"],"items":{"$ref":"#/definitions/PackageName"}},"no-extra":{"description":"Exclude the specified optional dependencies if `all-extras` is supplied.","type":["array","null"],"items":{"$ref":"#/definitions/ExtraName"}},"no-header":{"description":"Exclude the comment header at the top of output file generated by `uv pip compile`.","type":["boolean","null"]},"no-index":{"description":"Ignore all registry indexes (e.g., PyPI), instead relying on direct URL dependencies and those provided via `--find-links`.","type":["boolean","null"]},"no-sources":{"description":"Ignore the `tool.uv.sources` table when resolving dependencies. Used to lock against the standards-compliant, publishable package metadata, as opposed to using any local or Git sources.","type":["boolean","null"]},"no-strip-extras":{"description":"Include extras in the output file.\n\nBy default, uv strips extras, as any packages pulled in by the extras are already included as dependencies in the output file directly. Further, output files generated with `--no-strip-extras` cannot be used as constraints files in `install` and `sync` invocations.","type":["boolean","null"]},"no-strip-markers":{"description":"Include environment markers in the output file generated by `uv pip compile`.\n\nBy default, uv strips environment markers, as the resolution generated by `compile` is only guaranteed to be correct for the target environment.","type":["boolean","null"]},"only-binary":{"description":"Only use pre-built wheels; don't build source distributions.\n\nWhen enabled, resolving will not run code from the given packages. The cached wheels of already-built source distributions will be reused, but operations that require building distributions will exit with an error.\n\nMultiple packages may be provided. Disable binaries for all packages with `:all:`. Clear previously specified packages with `:none:`.","type":["array","null"],"items":{"$ref":"#/definitions/PackageNameSpecifier"}},"output-file":{"description":"Write the requirements generated by `uv pip compile` to the given `requirements.txt` file.\n\nIf the file already exists, the existing versions will be preferred when resolving dependencies, unless `--upgrade` is also specified.","type":["string","null"]},"prefix":{"description":"Install packages into `lib`, `bin`, and other top-level folders under the specified directory, as if a virtual environment were present at that location.\n\nIn general, prefer the use of `--python` to install into an alternate environment, as scripts and other artifacts installed via `--prefix` will reference the installing interpreter, rather than any interpreter added to the `--prefix` directory, rendering them non-portable.","type":["string","null"]},"prerelease":{"description":"The strategy to use when considering pre-release versions.\n\nBy default, uv will accept pre-releases for packages that _only_ publish pre-releases, along with first-party requirements that contain an explicit pre-release marker in the declared specifiers (`if-necessary-or-explicit`).","anyOf":[{"$ref":"#/definitions/PrereleaseMode"},{"type":"null"}]},"python":{"description":"The Python interpreter into which packages should be installed.\n\nBy default, uv installs into the virtual environment in the current working directory or any parent directory. The `--python` option allows you to specify a different interpreter, which is intended for use in continuous integration (CI) environments or other automated workflows.\n\nSupported formats: - `3.10` looks for an installed Python 3.10 in the registry on Windows (see `py --list-paths`), or `python3.10` on Linux and macOS. - `python3.10` or `python.exe` looks for a binary with the given name in `PATH`. - `/home/ferris/.local/bin/python3.10` uses the exact Python at the given path.","type":["string","null"]},"python-platform":{"description":"The platform for which requirements should be resolved.\n\nRepresented as a \"target triple\", a string that describes the target platform in terms of its CPU, vendor, and operating system name, like `x86_64-unknown-linux-gnu` or `aarch64-apple-darwin`.","anyOf":[{"$ref":"#/definitions/TargetTriple"},{"type":"null"}]},"python-version":{"description":"The minimum Python version that should be supported by the resolved requirements (e.g., `3.8` or `3.8.17`).\n\nIf a patch version is omitted, the minimum patch version is assumed. For example, `3.8` is mapped to `3.8.0`.","anyOf":[{"$ref":"#/definitions/PythonVersion"},{"type":"null"}]},"reinstall":{"description":"Reinstall all packages, regardless of whether they're already installed. Implies `refresh`.","type":["boolean","null"]},"reinstall-package":{"description":"Reinstall a specific package, regardless of whether it's already installed. Implies `refresh-package`.","type":["array","null"],"items":{"$ref":"#/definitions/PackageName"}},"require-hashes":{"description":"Require a matching hash for each requirement.\n\nHash-checking mode is all or nothing. If enabled, _all_ requirements must be provided with a corresponding hash or set of hashes. Additionally, if enabled, _all_ requirements must either be pinned to exact versions (e.g., `==1.0.0`), or be specified via direct URL.\n\nHash-checking mode introduces a number of additional constraints:\n\n- Git dependencies are not supported. - Editable installs are not supported. - Local dependencies are not supported, unless they point to a specific wheel (`.whl`) or source archive (`.zip`, `.tar.gz`), as opposed to a directory.","type":["boolean","null"]},"resolution":{"description":"The strategy to use when selecting between the different compatible versions for a given package requirement.\n\nBy default, uv will use the latest compatible version of each package (`highest`).","anyOf":[{"$ref":"#/definitions/ResolutionMode"},{"type":"null"}]},"strict":{"description":"Validate the Python environment, to detect packages with missing dependencies and other issues.","type":["boolean","null"]},"system":{"description":"Install packages into the system Python environment.\n\nBy default, uv installs into the virtual environment in the current working directory or any parent directory. The `--system` option instructs uv to instead use the first Python found in the system `PATH`.\n\nWARNING: `--system` is intended for use in continuous integration (CI) environments and should be used with caution, as it can modify the system Python installation.","type":["boolean","null"]},"target":{"description":"Install packages into the specified directory, rather than into the virtual or system Python environment. The packages will be installed at the top-level of the directory.","type":["string","null"]},"universal":{"description":"Perform a universal resolution, attempting to generate a single `requirements.txt` output file that is compatible with all operating systems, architectures, and Python implementations.\n\nIn universal mode, the current Python version (or user-provided `--python-version`) will be treated as a lower bound. For example, `--universal --python-version 3.7` would produce a universal resolution for Python 3.7 and later.","type":["boolean","null"]},"upgrade":{"description":"Allow package upgrades, ignoring pinned versions in any existing output file.","type":["boolean","null"]},"upgrade-package":{"description":"Allow upgrades for a specific package, ignoring pinned versions in any existing output file.\n\nAccepts both standalone package names (`ruff`) and version specifiers (`ruff<0.5.0`).","type":["array","null"],"items":{"$ref":"#/definitions/Requirement"}},"verify-hashes":{"description":"Validate any hashes provided in the requirements file.\n\nUnlike `--require-hashes`, `--verify-hashes` does not require that all requirements have hashes; instead, it will limit itself to verifying the hashes of those requirements that do include them.","type":["boolean","null"]}},"additionalProperties":false},"PrereleaseMode":{"oneOf":[{"description":"Disallow all pre-release versions.","type":"string","enum":["disallow"]},{"description":"Allow all pre-release versions.","type":"string","enum":["allow"]},{"description":"Allow pre-release versions if all versions of a package are pre-release.","type":"string","enum":["if-necessary"]},{"description":"Allow pre-release versions for first-party packages with explicit pre-release markers in their version requirements.","type":"string","enum":["explicit"]},{"description":"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.","type":"string","enum":["if-necessary-or-explicit"]}]},"PythonDownloads":{"oneOf":[{"description":"Automatically download managed Python installations when needed.","type":"string","enum":["automatic"]},{"description":"Do not automatically download managed Python installations; require explicit installation.","type":"string","enum":["manual"]},{"description":"Do not ever allow Python downloads.","type":"string","enum":["never"]}]},"PythonPreference":{"oneOf":[{"description":"Only use managed Python installations; never use system Python installations.","type":"string","enum":["only-managed"]},{"description":"Prefer managed Python installations over system Python installations.\n\nSystem Python installations are still preferred over downloading managed Python versions. Use `only-managed` to always fetch a managed Python version.","type":"string","enum":["managed"]},{"description":"Prefer system Python installations over managed Python installations.\n\nIf a system Python installation cannot be found, a managed Python installation can be used.","type":"string","enum":["system"]},{"description":"Only use system Python installations; never use managed Python installations.","type":"string","enum":["only-system"]}]},"PythonVersion":{"description":"A Python version specifier, e.g. `3.11` or `3.12.4`.","type":"string","pattern":"^3\\.\\d+(\\.\\d+)?$"},"RequiredVersion":{"description":"A version specifier, e.g. `>=0.5.0` or `==0.5.0`.","type":"string"},"Requirement":{"description":"A PEP 508 dependency specifier, e.g., `ruff >= 0.6.0`","type":"string"},"ResolutionMode":{"oneOf":[{"description":"Resolve the highest compatible version of each package.","type":"string","enum":["highest"]},{"description":"Resolve the lowest compatible version of each package.","type":"string","enum":["lowest"]},{"description":"Resolve the lowest compatible version of any direct dependencies, and the highest compatible version of any transitive dependencies.","type":"string","enum":["lowest-direct"]}]},"SchemaConflictItem":{"description":"A single item in a conflicting set.\n\nEach item is a pair of an (optional) package and a corresponding extra or group name for that package.","type":"object","properties":{"extra":{"default":null,"anyOf":[{"$ref":"#/definitions/ExtraName"},{"type":"null"}]},"group":{"default":null,"anyOf":[{"$ref":"#/definitions/GroupName"},{"type":"null"}]},"package":{"default":null,"anyOf":[{"$ref":"#/definitions/PackageName"},{"type":"null"}]}}},"SchemaConflictSet":{"description":"Like [`ConflictSet`], but for deserialization in `pyproject.toml`.\n\nThe schema format is different from the in-memory format. Specifically, the schema format does not allow specifying the package name (or will make it optional in the future), where as the in-memory format needs the package name.","type":"array","items":{"$ref":"#/definitions/SchemaConflictItem"}},"SchemaConflicts":{"description":"Like [`Conflicts`], but for deserialization in `pyproject.toml`.\n\nThe schema format is different from the in-memory format. Specifically, the schema format does not allow specifying the package name (or will make it optional in the future), where as the in-memory format needs the package name.\n\nN.B. `Conflicts` is still used for (de)serialization. Specifically, in the lock file, where the package name is required.","type":"array","items":{"$ref":"#/definitions/SchemaConflictSet"}},"Source":{"description":"A `tool.uv.sources` value.","anyOf":[{"description":"A remote Git repository, available over HTTPS or SSH.\n\nExample: ```toml flask = { git = \"https://github.com/pallets/flask\", tag = \"3.0.0\" } ```","type":"object","required":["git"],"properties":{"branch":{"type":["string","null"]},"extra":{"anyOf":[{"$ref":"#/definitions/ExtraName"},{"type":"null"}]},"git":{"description":"The repository URL (without the `git+` prefix).","type":"string","format":"uri"},"group":{"anyOf":[{"$ref":"#/definitions/GroupName"},{"type":"null"}]},"marker":{"$ref":"#/definitions/MarkerTree"},"rev":{"type":["string","null"]},"subdirectory":{"description":"The path to the directory with the `pyproject.toml`, if it's not in the archive root.","anyOf":[{"$ref":"#/definitions/String"},{"type":"null"}]},"tag":{"type":["string","null"]}},"additionalProperties":false},{"description":"A remote `http://` or `https://` URL, either a wheel (`.whl`) or a source distribution (`.zip`, `.tar.gz`).\n\nExample: ```toml flask = { url = \"https://files.pythonhosted.org/packages/61/80/ffe1da13ad9300f87c93af113edd0638c75138c42a0994becfacac078c06/flask-3.0.3-py3-none-any.whl\" } ```","type":"object","required":["url"],"properties":{"extra":{"anyOf":[{"$ref":"#/definitions/ExtraName"},{"type":"null"}]},"group":{"anyOf":[{"$ref":"#/definitions/GroupName"},{"type":"null"}]},"marker":{"$ref":"#/definitions/MarkerTree"},"subdirectory":{"description":"For source distributions, the path to the directory with the `pyproject.toml`, if it's not in the archive root.","anyOf":[{"$ref":"#/definitions/String"},{"type":"null"}]},"url":{"type":"string","format":"uri"}},"additionalProperties":false},{"description":"The path to a dependency, either a wheel (a `.whl` file), source distribution (a `.zip` or `.tar.gz` file), or source tree (i.e., a directory containing a `pyproject.toml` or `setup.py` file in the root).","type":"object","required":["path"],"properties":{"editable":{"description":"`false` by default.","type":["boolean","null"]},"extra":{"anyOf":[{"$ref":"#/definitions/ExtraName"},{"type":"null"}]},"group":{"anyOf":[{"$ref":"#/definitions/GroupName"},{"type":"null"}]},"marker":{"$ref":"#/definitions/MarkerTree"},"path":{"$ref":"#/definitions/String"}},"additionalProperties":false},{"description":"A dependency pinned to a specific index, e.g., `torch` after setting `torch` to `https://download.pytorch.org/whl/cu118`.","type":"object","required":["index"],"properties":{"extra":{"anyOf":[{"$ref":"#/definitions/ExtraName"},{"type":"null"}]},"group":{"anyOf":[{"$ref":"#/definitions/GroupName"},{"type":"null"}]},"index":{"$ref":"#/definitions/IndexName"},"marker":{"$ref":"#/definitions/MarkerTree"}},"additionalProperties":false},{"description":"A dependency on another package in the workspace.","type":"object","required":["workspace"],"properties":{"extra":{"anyOf":[{"$ref":"#/definitions/ExtraName"},{"type":"null"}]},"group":{"anyOf":[{"$ref":"#/definitions/GroupName"},{"type":"null"}]},"marker":{"$ref":"#/definitions/MarkerTree"},"workspace":{"description":"When set to `false`, the package will be fetched from the remote index, rather than included as a workspace package.","type":"boolean"}},"additionalProperties":false}]},"Sources":{"$ref":"#/definitions/SourcesWire"},"SourcesWire":{"anyOf":[{"$ref":"#/definitions/Source"},{"type":"array","items":{"$ref":"#/definitions/Source"}}]},"StaticMetadata":{"description":"A subset of the Python Package Metadata 2.3 standard as specified in <https://packaging.python.org/specifications/core-metadata/>.","type":"object","required":["name"],"properties":{"name":{"$ref":"#/definitions/PackageName"},"provides-extras":{"default":[],"type":"array","items":{"$ref":"#/definitions/ExtraName"}},"requires-dist":{"default":[],"type":"array","items":{"$ref":"#/definitions/Requirement"}},"requires-python":{"description":"PEP 508-style Python requirement, e.g., `>=3.10`","type":["string","null"]},"version":{"description":"PEP 440-style package version, e.g., `1.2.3`","type":["string","null"]}}},"String":{"type":"string"},"TargetTriple":{"description":"The supported target triples. Each triple consists of an architecture, vendor, and operating system.\n\nSee: <https://doc.rust-lang.org/nightly/rustc/platform-support.html>","oneOf":[{"description":"An alias for `x86_64-pc-windows-msvc`, the default target for Windows.","type":"string","enum":["windows"]},{"description":"An alias for `x86_64-unknown-linux-gnu`, the default target for Linux.","type":"string","enum":["linux"]},{"description":"An alias for `aarch64-apple-darwin`, the default target for macOS.","type":"string","enum":["macos"]},{"description":"A 64-bit x86 Windows target.","type":"string","enum":["x86_64-pc-windows-msvc"]},{"description":"A 32-bit x86 Windows target.","type":"string","enum":["i686-pc-windows-msvc"]},{"description":"An x86 Linux target. Equivalent to `x86_64-manylinux_2_17`.","type":"string","enum":["x86_64-unknown-linux-gnu"]},{"description":"An ARM-based macOS target, as seen on Apple Silicon devices\n\nBy default, assumes the least-recent, non-EOL macOS version (12.0), but respects the `MACOSX_DEPLOYMENT_TARGET` environment variable if set.","type":"string","enum":["aarch64-apple-darwin"]},{"description":"An x86 macOS target.\n\nBy default, assumes the least-recent, non-EOL macOS version (12.0), but respects the `MACOSX_DEPLOYMENT_TARGET` environment variable if set.","type":"string","enum":["x86_64-apple-darwin"]},{"description":"An ARM64 Linux target. Equivalent to `aarch64-manylinux_2_17`.","type":"string","enum":["aarch64-unknown-linux-gnu"]},{"description":"An ARM64 Linux target.","type":"string","enum":["aarch64-unknown-linux-musl"]},{"description":"An `x86_64` Linux target.","type":"string","enum":["x86_64-unknown-linux-musl"]},{"description":"An `x86_64` target for the `manylinux2014` platform. Equivalent to `x86_64-manylinux_2_17`.","type":"string","enum":["x86_64-manylinux2014"]},{"description":"An `x86_64` target for the `manylinux_2_17` platform.","type":"string","enum":["x86_64-manylinux_2_17"]},{"description":"An `x86_64` target for the `manylinux_2_28` platform.","type":"string","enum":["x86_64-manylinux_2_28"]},{"description":"An `x86_64` target for the `manylinux_2_31` platform.","type":"string","enum":["x86_64-manylinux_2_31"]},{"description":"An `x86_64` target for the `manylinux_2_32` platform.","type":"string","enum":["x86_64-manylinux_2_32"]},{"description":"An `x86_64` target for the `manylinux_2_33` platform.","type":"string","enum":["x86_64-manylinux_2_33"]},{"description":"An `x86_64` target for the `manylinux_2_34` platform.","type":"string","enum":["x86_64-manylinux_2_34"]},{"description":"An `x86_64` target for the `manylinux_2_35` platform.","type":"string","enum":["x86_64-manylinux_2_35"]},{"description":"An `x86_64` target for the `manylinux_2_36` platform.","type":"string","enum":["x86_64-manylinux_2_36"]},{"description":"An `x86_64` target for the `manylinux_2_37` platform.","type":"string","enum":["x86_64-manylinux_2_37"]},{"description":"An `x86_64` target for the `manylinux_2_38` platform.","type":"string","enum":["x86_64-manylinux_2_38"]},{"description":"An `x86_64` target for the `manylinux_2_39` platform.","type":"string","enum":["x86_64-manylinux_2_39"]},{"description":"An `x86_64` target for the `manylinux_2_40` platform.","type":"string","enum":["x86_64-manylinux_2_40"]},{"description":"An ARM64 target for the `manylinux2014` platform. Equivalent to `aarch64-manylinux_2_17`.","type":"string","enum":["aarch64-manylinux2014"]},{"description":"An ARM64 target for the `manylinux_2_17` platform.","type":"string","enum":["aarch64-manylinux_2_17"]},{"description":"An ARM64 target for the `manylinux_2_28` platform.","type":"string","enum":["aarch64-manylinux_2_28"]},{"description":"An ARM64 target for the `manylinux_2_31` platform.","type":"string","enum":["aarch64-manylinux_2_31"]},{"description":"An ARM64 target for the `manylinux_2_32` platform.","type":"string","enum":["aarch64-manylinux_2_32"]},{"description":"An ARM64 target for the `manylinux_2_33` platform.","type":"string","enum":["aarch64-manylinux_2_33"]},{"description":"An ARM64 target for the `manylinux_2_34` platform.","type":"string","enum":["aarch64-manylinux_2_34"]},{"description":"An ARM64 target for the `manylinux_2_35` platform.","type":"string","enum":["aarch64-manylinux_2_35"]},{"description":"An ARM64 target for the `manylinux_2_36` platform.","type":"string","enum":["aarch64-manylinux_2_36"]},{"description":"An ARM64 target for the `manylinux_2_37` platform.","type":"string","enum":["aarch64-manylinux_2_37"]},{"description":"An ARM64 target for the `manylinux_2_38` platform.","type":"string","enum":["aarch64-manylinux_2_38"]},{"description":"An ARM64 target for the `manylinux_2_39` platform.","type":"string","enum":["aarch64-manylinux_2_39"]},{"description":"An ARM64 target for the `manylinux_2_40` platform.","type":"string","enum":["aarch64-manylinux_2_40"]}]},"ToolUvSources":{"type":"object","additionalProperties":{"$ref":"#/definitions/Sources"}},"ToolUvWorkspace":{"type":"object","properties":{"exclude":{"description":"Packages to exclude as workspace members. If a package matches both `members` and `exclude`, it will be excluded.\n\nSupports both globs and explicit paths.\n\nFor more information on the glob syntax, refer to the [`glob` documentation](https://docs.rs/glob/latest/glob/struct.Pattern.html).","type":["array","null"],"items":{"$ref":"#/definitions/String"}},"members":{"description":"Packages to include as workspace members.\n\nSupports both globs and explicit paths.\n\nFor more information on the glob syntax, refer to the [`glob` documentation](https://docs.rs/glob/latest/glob/struct.Pattern.html).","type":["array","null"],"items":{"$ref":"#/definitions/String"}}},"additionalProperties":false},"TrustedHost":{"description":"A host or host-port pair.","type":"string"},"TrustedPublishing":{"oneOf":[{"type":"string","enum":["always","never"]},{"description":"Try trusted publishing when we're already in GitHub Actions, continue if that fails.","type":"string","enum":["automatic"]}]}}}
</schema>

[User] Provide a JSON object that satisfies the schema "CombinedOptions". Here are the required top‑level fields: none (all optional). Return only the valid JSON object.

CombinedOptions

Metadata and configuration for uv.

Allow insecure connections to host.

Expects to receive either a hostname (e.g., `localhost`), a host-port pair (e.g., `localhost:8080`), or a URL (e.g., `https://localhost`).

WARNING: Hosts included in this list will not be verified against the system's certificate store. Only use `--allow-insecure-host` in a secure network with verified sources, as it bypasses SSL verification and could expose you to MITM attacks.

Path to the cache directory.

Defaults to `$HOME/Library/Caches/uv` on macOS, `$XDG_CACHE_HOME/uv` or `$HOME/.cache/uv` on Linux, and `%LOCALAPPDATA%\uv\cache` on Windows.

The keys to consider when caching builds for the project.

Cache keys enable you to specify the files or directories that should trigger a rebuild when modified. By default, uv will rebuild a project whenever the `pyproject.toml`, `setup.py`, or `setup.cfg` files in the project directory are modified, i.e.:

```toml cache-keys = [{ file = "pyproject.toml" }, { file = "setup.py" }, { file = "setup.cfg" }] ```

As an example: if a project uses dynamic metadata to read its dependencies from a `requirements.txt` file, you can specify `cache-keys = [{ file = "requirements.txt" }, { file = "pyproject.toml" }]` to ensure that the project is rebuilt whenever the `requirements.txt` file is modified (in addition to watching the `pyproject.toml`).

Globs are supported, following the syntax of the [`glob`](https://docs.rs/glob/0.3.1/glob/struct.Pattern.html) crate. For example, to invalidate the cache whenever a `.toml` file in the project directory or any of its subdirectories is modified, you can specify `cache-keys = [{ file = "**/*.toml" }]`. Note that the use of globs can be expensive, as uv may need to walk the filesystem to determine whether any files have changed.

Cache keys can also include version control information. For example, if a project uses `setuptools_scm` to read its version from a Git commit, you can specify `cache-keys = [{ git = { commit = true }, { file = "pyproject.toml" }]` to include the current Git commit hash in the cache key (in addition to the `pyproject.toml`). Git tags are also supported via `cache-keys = [{ git = { commit = true, tags = true } }]`.

Cache keys can also include environment variables. For example, if a project relies on `MACOSX_DEPLOYMENT_TARGET` or other environment variables to determine its behavior, you can specify `cache-keys = [{ env = "MACOSX_DEPLOYMENT_TARGET" }]` to invalidate the cache whenever the environment variable changes.

Cache keys only affect the project defined by the `pyproject.toml` in which they're specified (as opposed to, e.g., affecting all members in a workspace), and all paths and globs are interpreted as relative to the project directory.

Check an index URL for existing files to skip duplicate uploads.

This option allows retrying publishing that failed after only some, but not all files have been uploaded, and handles error due to parallel uploads of the same file.

Before uploading, the index is checked. If the exact same file already exists in the index, the file will not be uploaded. If an error occurred during the upload, the index is checked again, to handle cases where the identical file was uploaded twice in parallel.

The exact behavior will vary based on the index. When uploading to PyPI, uploading the same file succeeds even without `--check-url`, while most other indexes error.

The index must provide one of the supported hashes (SHA-256, SHA-384, or SHA-512).

Compile Python files to bytecode after installation.

By default, uv does not compile Python (`.py`) files to bytecode (`__pycache__/*.pyc`); instead, compilation is performed lazily the first time a module is imported. For use-cases in which start time is critical, such as CLI applications and Docker containers, this option can be enabled to trade longer installation times for faster start times.

When enabled, uv will process the entire site-packages directory (including packages that are not being modified by the current operation) for consistency. Like pip, it will also ignore errors.

The maximum number of source distributions that uv will build concurrently at any given time.

Defaults to the number of available CPU cores.

The maximum number of in-flight concurrent downloads that uv will perform at any given time.

The number of threads used when installing and unzipping packages.

Defaults to the number of available CPU cores.

Settings to pass to the [PEP 517](https://peps.python.org/pep-0517/) build backend, specified as `KEY=VALUE` pairs.

A list of sets of conflicting groups or extras.

PEP 508-style requirements, e.g., `ruff==0.5.0`, or `ruff @ https://...`.

The list of `dependency-groups` to install by default.

Pre-defined static metadata for dependencies of the project (direct or transitive). When provided, enables the resolver to use the specified metadata instead of querying the registry or building the relevant package from source.

Metadata should be provided in adherence with the [Metadata 2.3](https://packaging.python.org/en/latest/specifications/core-metadata/) standard, though only the following fields are respected:

- `name`: The name of the package. - (Optional) `version`: The version of the package. If omitted, the metadata will be applied to all versions of the package. - (Optional) `requires-dist`: The dependencies of the package (e.g., `werkzeug>=0.14`). - (Optional) `requires-python`: The Python version required by the package (e.g., `>=3.10`). - (Optional) `provides-extras`: The extras provided by the package.

A list of environment markers, e.g., `python_version >= '3.6'`.

Limit candidate packages to those that were uploaded prior to the given date.

Accepts both [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339.html) timestamps (e.g., `2006-12-02T02:07:43Z`) and local dates in the same format (e.g., `2006-12-02`) in your system's configured time zone.

Extra URLs of package indexes to use, in addition to `--index-url`.

Accepts either a repository compliant with [PEP 503](https://peps.python.org/pep-0503/) (the simple repository API), or a local directory laid out in the same format.

All indexes provided via this flag take priority over the index specified by [`index_url`](#index-url) or [`index`](#index) with `default = true`. When multiple indexes are provided, earlier values take priority.

To control uv's resolution strategy when multiple indexes are present, see [`index_strategy`](#index-strategy).

(Deprecated: use `index` instead.)

Locations to search for candidate distributions, in addition to those found in the registry indexes.

If a path, the target must be a directory that contains packages as wheel files (`.whl`) or source distributions (e.g., `.tar.gz` or `.zip`) at the top level.

If a URL, the page must contain a flat list of links to package files adhering to the formats described above.

The strategy to use when selecting multiple versions of a given package across Python versions and platforms.

By default, uv will optimize for selecting the latest version of each package for each supported Python version (`requires-python`), while minimizing the number of selected versions across platforms.

Under `fewest`, uv will minimize the number of selected versions for each package, preferring older versions that are compatible with a wider range of supported Python versions or platforms.

The indexes to use when resolving dependencies.

Accepts either a repository compliant with [PEP 503](https://peps.python.org/pep-0503/) (the simple repository API), or a local directory laid out in the same format.

Indexes are considered in the order in which they're defined, such that the first-defined index has the highest priority. Further, the indexes provided by this setting are given higher priority than any indexes specified via [`index_url`](#index-url) or [`extra_index_url`](#extra-index-url). uv will only consider the first index that contains a given package, unless an alternative [index strategy](#index-strategy) is specified.

If an index is marked as `explicit = true`, it will be used exclusively for the dependencies that select it explicitly via `[tool.uv.sources]`, as in:

```toml [[tool.uv.index]] name = "pytorch" url = "https://download.pytorch.org/whl/cu121" explicit = true

[tool.uv.sources] torch = { index = "pytorch" } ```

If an index is marked as `default = true`, it will be moved to the end of the prioritized list, such that it is given the lowest priority when resolving packages. Additionally, marking an index as default will disable the PyPI default index.

The strategy to use when resolving against multiple index URLs.

By default, uv will stop at the first index on which a given package is available, and limit resolutions to those present on that first index (`first-index`). This prevents "dependency confusion" attacks, whereby an attacker can upload a malicious package under the same name to an alternate index.

The URL of the Python package index (by default: <https://pypi.org/simple>).

Accepts either a repository compliant with [PEP 503](https://peps.python.org/pep-0503/) (the simple repository API), or a local directory laid out in the same format.

The index provided by this setting is given lower priority than any indexes specified via [`extra_index_url`](#extra-index-url) or [`index`](#index).

(Deprecated: use `index` instead.)

Attempt to use `keyring` for authentication for index URLs.

At present, only `--keyring-provider subprocess` is supported, which configures uv to use the `keyring` CLI to handle authentication.

The method to use when installing packages from the global cache.

Defaults to `clone` (also known as Copy-on-Write) on macOS, and `hardlink` on Linux and Windows.

Whether the project is managed by uv. If `false`, uv will ignore the project when `uv run` is invoked.

Whether to load TLS certificates from the platform's native certificate store.

By default, uv loads certificates from the bundled `webpki-roots` crate. The `webpki-roots` are a reliable set of trust roots from Mozilla, and including them in uv improves portability and performance (especially on macOS).

However, in some cases, you may want to use the platform's native certificate store, especially if you're relying on a corporate trust root (e.g., for a mandatory proxy) that's included in your system's certificate store.

Don't install pre-built wheels.

The given packages will be built and installed from source. The resolver will still use pre-built wheels to extract package metadata, if available.

Don't install pre-built wheels for a specific package.

Disable isolation when building source distributions.

Assumes that build dependencies specified by [PEP 518](https://peps.python.org/pep-0518/) are already installed.

Disable isolation when building source distributions for a specific package.

Assumes that the packages' build dependencies specified by [PEP 518](https://peps.python.org/pep-0518/) are already installed.

Don't build source distributions for a specific package.

Avoid reading from or writing to the cache, instead using a temporary directory for the duration of the operation.

Ignore all registry indexes (e.g., PyPI), instead relying on direct URL dependencies and those provided via `--find-links`.

Ignore the `tool.uv.sources` table when resolving dependencies. Used to lock against the standards-compliant, publishable package metadata, as opposed to using any local or Git sources.

Disable network access, relying only on locally cached data and locally available files.

PEP 508-style requirements, e.g., `ruff==0.5.0`, or `ruff @ https://...`.

Whether the project should be considered a Python package, or a non-package ("virtual") project.

Packages are built and installed into the virtual environment in editable mode and thus require a build backend, while virtual projects are _not_ built or installed; instead, only their dependencies are included in the virtual environment.

Creating a package requires that a `build-system` is present in the `pyproject.toml`, and that the project adheres to a structure that adheres to the build backend's expectations (e.g., a `src` layout).

The strategy to use when considering pre-release versions.

By default, uv will accept pre-releases for packages that _only_ publish pre-releases, along with first-party requirements that contain an explicit pre-release marker in the declared specifiers (`if-necessary-or-explicit`).

Whether to enable experimental, preview features.

The URL for publishing packages to the Python package index (by default: <https://upload.pypi.org/legacy/>).

Mirror URL to use for downloading managed PyPy installations.

By default, managed PyPy installations are downloaded from [downloads.python.org](https://downloads.python.org/). This variable can be set to a mirror URL to use a different source for PyPy installations. The provided URL will replace `https://downloads.python.org/pypy` in, e.g., `https://downloads.python.org/pypy/pypy3.8-v7.3.7-osx64.tar.bz2`.

Distributions can be read from a local directory by using the `file://` URL scheme.

Whether to allow Python downloads.

Mirror URL for downloading managed Python installations.

By default, managed Python installations are downloaded from [`python-build-standalone`](https://github.com/astral-sh/python-build-standalone). This variable can be set to a mirror URL to use a different source for Python installations. The provided URL will replace `https://github.com/astral-sh/python-build-standalone/releases/download` in, e.g., `https://github.com/astral-sh/python-build-standalone/releases/download/20240713/cpython-3.12.4%2B20240713-aarch64-apple-darwin-install_only.tar.gz`.

Distributions can be read from a local directory by using the `file://` URL scheme.

Whether to prefer using Python installations that are already present on the system, or those that are downloaded and installed by uv.

Reinstall all packages, regardless of whether they're already installed. Implies `refresh`.

Reinstall a specific package, regardless of whether it's already installed. Implies `refresh-package`.

Enforce a requirement on the version of uv.

If the version of uv does not meet the requirement at runtime, uv will exit with an error.

Accepts a [PEP 440](https://peps.python.org/pep-0440/) specifier, like `==0.5.0` or `>=0.5.0`.

The strategy to use when selecting between the different compatible versions for a given package requirement.

By default, uv will use the latest compatible version of each package (`highest`).

The sources to use when resolving dependencies.

`tool.uv.sources` enriches the dependency metadata with additional sources, incorporated during development. A dependency source can be a Git repository, a URL, a local path, or an alternative registry.

See [Dependencies](https://docs.astral.sh/uv/concepts/projects/dependencies/) for more.

Configure trusted publishing via GitHub Actions.

By default, uv checks for trusted publishing when running in GitHub Actions, but ignores it if it isn't configured or the workflow doesn't have enough permissions (e.g., a pull request from a fork).

Allow package upgrades, ignoring pinned versions in any existing output file.

Allow upgrades for a specific package, ignoring pinned versions in any existing output file.

Accepts both standalone package names (`ruff`) and version specifiers (`ruff<0.5.0`).

The workspace definition for the project, if any.

Indicate the style of annotation comments, used to indicate the dependencies that requested each package.

Render the annotations on a single, comma-separated line.

Render each annotation on its own line.

Ex) `"Cargo.lock"` or `"**/*.toml"`

Ex) `{ file = "Cargo.lock" }` or `{ file = "**/*.toml" }`

Ex) `{ git = true }` or `{ git = { commit = true, tags = false } }`

Ex) `{ env = "UV_CACHE_INFO" }`

The value consists of a single string.

The value consists of a list of strings.

Settings to pass to a PEP 517 build backend, structured as a map from (string) key to string or list of strings.

See: <https://peps.python.org/pep-0517/#config-settings>

Exclude distributions uploaded after the given timestamp.

Accepts both RFC 3339 timestamps (e.g., `2006-12-02T02:07:43Z`) and local dates in the same format (e.g., `2006-12-02`).

The normalized name of an extra dependency.

Converts the name to lowercase and collapses runs of `-`, `_`, and `.` down to a single `-`. For example, `---`, `.`, and `__` are all converted to a single `-`.

See: - <https://peps.python.org/pep-0685/#specification/> - <https://packaging.python.org/en/latest/specifications/name-normalization/>

Optimize for selecting the fewest number of versions for each package. Older versions may be preferred if they are compatible with a wider range of supported Python versions or platforms.

Optimize for selecting latest supported version of each package, for each supported Python version.

The normalized name of a dependency group.

See: - <https://peps.python.org/pep-0735/> - <https://packaging.python.org/en/latest/specifications/name-normalization/>

Mark the index as the default index.

By default, uv uses PyPI as the default index, such that even if additional indexes are defined via `[[tool.uv.index]]`, PyPI will still be used as a fallback for packages that aren't found elsewhere. To disable the PyPI default, set `default = true` on at least one other index.

Marking an index as default will move it to the front of the list of indexes, such that it is given the highest priority when resolving packages.

Mark the index as explicit.

Explicit indexes will _only_ be used when explicitly requested via a `[tool.uv.sources]` definition, as in:

```toml [[tool.uv.index]] name = "pytorch" url = "https://download.pytorch.org/whl/cu121" explicit = true

[tool.uv.sources] torch = { index = "pytorch" } ```

The name of the index.

Index names can be used to reference indexes elsewhere in the configuration. For example, you can pin a package to a specific index by name:

```toml [[tool.uv.index]] name = "pytorch" url = "https://download.pytorch.org/whl/cu121"

[tool.uv.sources] torch = { index = "pytorch" } ```

The URL of the upload endpoint.

When using `uv publish --index <name>`, this URL is used for publishing.

A configuration for the default index PyPI would look as follows:

```toml [[tool.uv.index]] name = "pypi" url = "https://pypi.org/simple" publish-url = "https://upload.pypi.org/legacy/" ```

The URL of the index.

Expects to receive a URL (e.g., `https://pypi.org/simple`) or a local path.

The normalized name of an index.

Index names may contain letters, digits, hyphens, underscores, and periods, and must be ASCII.

Only use results from the first index that returns a match for a given package name.

While this differs from pip's behavior, it's the default index strategy as it's the most secure.

Search for every package name across all indexes, exhausting the versions from the first index before moving on to the next.

In this strategy, we look for every package across all indexes. When resolving, we attempt to use versions from the indexes in order, such that we exhaust all available versions from the first index before moving on to the next. Further, if a version is found to be incompatible in the first index, we do not reconsider that version in subsequent indexes, even if the secondary index might contain compatible versions (e.g., variants of the same versions with different ABI tags or Python version constraints).

See: <https://peps.python.org/pep-0708/>

Search for every package name across all indexes, preferring the "best" version found. If a package version is in multiple indexes, only look at the entry for the first index.

In this strategy, we look for every package across all indexes. When resolving, we consider all versions from all indexes, choosing the "best" version found (typically, the highest compatible version).

This most closely matches pip's behavior, but exposes the resolver to "dependency confusion" attacks whereby malicious actors can publish packages to public indexes with the same name as internal packages, causing the resolver to install the malicious package in lieu of the intended internal package.

See: <https://peps.python.org/pep-0708/>

The URL of an index to use for fetching packages (e.g., `https://pypi.org/simple`).

Keyring provider type to use for credential lookup.

Do not use keyring for credential lookup.

Use the `keyring` command for credential lookup.

Clone (i.e., copy-on-write) packages from the wheel into the `site-packages` directory.

Copy packages from the wheel into the `site-packages` directory.

Hard link packages from the wheel into the `site-packages` directory.

Symbolically link packages from the wheel into the `site-packages` directory.

WARNING: The use of symlinks is discouraged, as they create tight coupling between the cache and the target environment. For example, clearing the cache (`uv cache clear`) will break all installed packages by way of removing the underlying source files. Use symlinks with caution.

A PEP 508-compliant marker expression, e.g., `sys_platform == 'Darwin'`

The normalized name of a package.

Converts the name to lowercase and collapses runs of `-`, `_`, and `.` down to a single `-`. For example, `---`, `.`, and `__` are all converted to a single `-`.

See: <https://packaging.python.org/en/latest/specifications/name-normalization/>

The name of a package, or `:all:` or `:none:` to select or omit all packages, respectively.

Settings that are specific to the `uv pip` command-line interface.

These values will be ignored when running commands outside the `uv pip` namespace (e.g., `uv lock`, `uvx`).

Include all optional dependencies.

Only applies to `pyproject.toml`, `setup.py`, and `setup.cfg` sources.

Allow `uv pip sync` with empty requirements, which will clear the environment of all packages.

The style of the annotation comments included in the output file, used to indicate the source of each package.

Allow uv to modify an `EXTERNALLY-MANAGED` Python installation.

WARNING: `--break-system-packages` is intended for use in continuous integration (CI) environments, when installing into Python installations that are managed by an external package manager, like `apt`. It should be used with caution, as such Python installations explicitly recommend against modifications by other package managers (like uv or pip).

Settings to pass to the [PEP 517](https://peps.python.org/pep-0517/) build backend, specified as `KEY=VALUE` pairs.

The header comment to include at the top of the output file generated by `uv pip compile`.

Used to reflect custom build scripts and commands that wrap `uv pip compile`.

Include `--no-binary` and `--only-binary` entries in the output file generated by `uv pip compile`.

Include `--find-links` entries in the output file generated by `uv pip compile`.

Include comment annotations indicating the index used to resolve each package (e.g., `# from https://pypi.org/simple`).

Include `--index-url` and `--extra-index-url` entries in the output file generated by `uv pip compile`.

Whether to emit a marker string indicating the conditions under which the set of pinned dependencies is valid.

The pinned dependencies may be valid even when the marker expression is false, but when the expression is true, the requirements are known to be correct.

Limit candidate packages to those that were uploaded prior to a given point in time.

Accepts a superset of [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339.html) (e.g., `2006-12-02T02:07:43Z`). A full timestamp is required to ensure that the resolver will behave consistently across timezones.

Include optional dependencies from the specified extra; may be provided more than once.

Only applies to `pyproject.toml`, `setup.py`, and `setup.cfg` sources.

Extra URLs of package indexes to use, in addition to `--index-url`.

Accepts either a repository compliant with [PEP 503](https://peps.python.org/pep-0503/) (the simple repository API), or a local directory laid out in the same format.

All indexes provided via this flag take priority over the index specified by [`index_url`](#index-url). When multiple indexes are provided, earlier values take priority.

To control uv's resolution strategy when multiple indexes are present, see [`index_strategy`](#index-strategy).

Include distribution hashes in the output file.

The URL of the Python package index (by default: <https://pypi.org/simple>).

Accepts either a repository compliant with [PEP 503](https://peps.python.org/pep-0503/) (the simple repository API), or a local directory laid out in the same format.

The index provided by this setting is given lower priority than any indexes specified via [`extra_index_url`](#extra-index-url).

Attempt to use `keyring` for authentication for index URLs.

At present, only `--keyring-provider subprocess` is supported, which configures uv to use the `keyring` CLI to handle authentication.

The method to use when installing packages from the global cache.

Defaults to `clone` (also known as Copy-on-Write) on macOS, and `hardlink` on Linux and Windows.

Exclude comment annotations indicating the source of each package from the output file generated by `uv pip compile`.

Don't install pre-built wheels.

The given packages will be built and installed from source. The resolver will still use pre-built wheels to extract package metadata, if available.

Multiple packages may be provided. Disable binaries for all packages with `:all:`. Clear previously specified packages with `:none:`.

Don't build source distributions.

When enabled, resolving will not run arbitrary Python code. The cached wheels of already-built source distributions will be reused, but operations that require building distributions will exit with an error.

Alias for `--only-binary :all:`.

Disable isolation when building source distributions.

Assumes that build dependencies specified by [PEP 518](https://peps.python.org/pep-0518/) are already installed.

Ignore package dependencies, instead only add those packages explicitly listed on the command line to the resulting requirements file.

Specify a package to omit from the output resolution. Its dependencies will still be included in the resolution. Equivalent to pip-compile's `--unsafe-package` option.

Exclude the specified optional dependencies if `all-extras` is supplied.

Exclude the comment header at the top of output file generated by `uv pip compile`.

Ignore all registry indexes (e.g., PyPI), instead relying on direct URL dependencies and those provided via `--find-links`.

Ignore the `tool.uv.sources` table when resolving dependencies. Used to lock against the standards-compliant, publishable package metadata, as opposed to using any local or Git sources.

Include extras in the output file.

By default, uv strips extras, as any packages pulled in by the extras are already included as dependencies in the output file directly. Further, output files generated with `--no-strip-extras` cannot be used as constraints files in `install` and `sync` invocations.

Include environment markers in the output file generated by `uv pip compile`.

By default, uv strips environment markers, as the resolution generated by `compile` is only guaranteed to be correct for the target environment.

Only use pre-built wheels; don't build source distributions.

When enabled, resolving will not run code from the given packages. The cached wheels of already-built source distributions will be reused, but operations that require building distributions will exit with an error.

Multiple packages may be provided. Disable binaries for all packages with `:all:`. Clear previously specified packages with `:none:`.

Write the requirements generated by `uv pip compile` to the given `requirements.txt` file.

If the file already exists, the existing versions will be preferred when resolving dependencies, unless `--upgrade` is also specified.

Install packages into `lib`, `bin`, and other top-level folders under the specified directory, as if a virtual environment were present at that location.

In general, prefer the use of `--python` to install into an alternate environment, as scripts and other artifacts installed via `--prefix` will reference the installing interpreter, rather than any interpreter added to the `--prefix` directory, rendering them non-portable.

The Python interpreter into which packages should be installed.

By default, uv installs into the virtual environment in the current working directory or any parent directory. The `--python` option allows you to specify a different interpreter, which is intended for use in continuous integration (CI) environments or other automated workflows.

Supported formats: - `3.10` looks for an installed Python 3.10 in the registry on Windows (see `py --list-paths`), or `python3.10` on Linux and macOS. - `python3.10` or `python.exe` looks for a binary with the given name in `PATH`. - `/home/ferris/.local/bin/python3.10` uses the exact Python at the given path.

The platform for which requirements should be resolved.

Represented as a "target triple", a string that describes the target platform in terms of its CPU, vendor, and operating system name, like `x86_64-unknown-linux-gnu` or `aarch64-apple-darwin`.

The minimum Python version that should be supported by the resolved requirements (e.g., `3.8` or `3.8.17`).

If a patch version is omitted, the minimum patch version is assumed. For example, `3.8` is mapped to `3.8.0`.

Reinstall all packages, regardless of whether they're already installed. Implies `refresh`.

Reinstall a specific package, regardless of whether it's already installed. Implies `refresh-package`.

Require a matching hash for each requirement.

Hash-checking mode is all or nothing. If enabled, _all_ requirements must be provided with a corresponding hash or set of hashes. Additionally, if enabled, _all_ requirements must either be pinned to exact versions (e.g., `==1.0.0`), or be specified via direct URL.

Hash-checking mode introduces a number of additional constraints:

- Git dependencies are not supported. - Editable installs are not supported. - Local dependencies are not supported, unless they point to a specific wheel (`.whl`) or source archive (`.zip`, `.tar.gz`), as opposed to a directory.

The strategy to use when selecting between the different compatible versions for a given package requirement.

By default, uv will use the latest compatible version of each package (`highest`).

Validate the Python environment, to detect packages with missing dependencies and other issues.

Install packages into the system Python environment.

By default, uv installs into the virtual environment in the current working directory or any parent directory. The `--system` option instructs uv to instead use the first Python found in the system `PATH`.

WARNING: `--system` is intended for use in continuous integration (CI) environments and should be used with caution, as it can modify the system Python installation.

Install packages into the specified directory, rather than into the virtual or system Python environment. The packages will be installed at the top-level of the directory.

Perform a universal resolution, attempting to generate a single `requirements.txt` output file that is compatible with all operating systems, architectures, and Python implementations.

In universal mode, the current Python version (or user-provided `--python-version`) will be treated as a lower bound. For example, `--universal --python-version 3.7` would produce a universal resolution for Python 3.7 and later.

Allow package upgrades, ignoring pinned versions in any existing output file.

Allow upgrades for a specific package, ignoring pinned versions in any existing output file.

Accepts both standalone package names (`ruff`) and version specifiers (`ruff<0.5.0`).

Validate any hashes provided in the requirements file.

Unlike `--require-hashes`, `--verify-hashes` does not require that all requirements have hashes; instead, it will limit itself to verifying the hashes of those requirements that do include them.

Disallow all pre-release versions.

Allow all pre-release versions.

Allow pre-release versions if all versions of a package are pre-release.

Allow pre-release versions for first-party packages with explicit pre-release markers in their version requirements.

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.

Automatically download managed Python installations when needed.

Do not automatically download managed Python installations; require explicit installation.

Do not ever allow Python downloads.

Only use managed Python installations; never use system Python installations.

Prefer managed Python installations over system Python installations.

System Python installations are still preferred over downloading managed Python versions. Use `only-managed` to always fetch a managed Python version.

Prefer system Python installations over managed Python installations.

If a system Python installation cannot be found, a managed Python installation can be used.

Only use system Python installations; never use managed Python installations.

A Python version specifier, e.g. `3.11` or `3.12.4`.

A version specifier, e.g. `>=0.5.0` or `==0.5.0`.

A PEP 508 dependency specifier, e.g., `ruff >= 0.6.0`

Resolve the highest compatible version of each package.

Resolve the lowest compatible version of each package.

Resolve the lowest compatible version of any direct dependencies, and the highest compatible version of any transitive dependencies.

A single item in a conflicting set.

Each item is a pair of an (optional) package and a corresponding extra or group name for that package.

Like [`ConflictSet`], but for deserialization in `pyproject.toml`.

The schema format is different from the in-memory format. Specifically, the schema format does not allow specifying the package name (or will make it optional in the future), where as the in-memory format needs the package name.

Like [`Conflicts`], but for deserialization in `pyproject.toml`.

The schema format is different from the in-memory format. Specifically, the schema format does not allow specifying the package name (or will make it optional in the future), where as the in-memory format needs the package name.

N.B. `Conflicts` is still used for (de)serialization. Specifically, in the lock file, where the package name is required.

A `tool.uv.sources` value.

A remote Git repository, available over HTTPS or SSH.

Example: ```toml flask = { git = "https://github.com/pallets/flask", tag = "3.0.0" } ```

The repository URL (without the `git+` prefix).

The path to the directory with the `pyproject.toml`, if it's not in the archive root.

A remote `http://` or `https://` URL, either a wheel (`.whl`) or a source distribution (`.zip`, `.tar.gz`).

Example: ```toml flask = { url = "https://files.pythonhosted.org/packages/61/80/ffe1da13ad9300f87c93af113edd0638c75138c42a0994becfacac078c06/flask-3.0.3-py3-none-any.whl" } ```

For source distributions, the path to the directory with the `pyproject.toml`, if it's not in the archive root.

The path to a dependency, either a wheel (a `.whl` file), source distribution (a `.zip` or `.tar.gz` file), or source tree (i.e., a directory containing a `pyproject.toml` or `setup.py` file in the root).

`false` by default.

A dependency pinned to a specific index, e.g., `torch` after setting `torch` to `https://download.pytorch.org/whl/cu118`.

A dependency on another package in the workspace.

When set to `false`, the package will be fetched from the remote index, rather than included as a workspace package.

A subset of the Python Package Metadata 2.3 standard as specified in <https://packaging.python.org/specifications/core-metadata/>.

PEP 508-style Python requirement, e.g., `>=3.10`

PEP 440-style package version, e.g., `1.2.3`

The supported target triples. Each triple consists of an architecture, vendor, and operating system.

See: <https://doc.rust-lang.org/nightly/rustc/platform-support.html>

An alias for `x86_64-pc-windows-msvc`, the default target for Windows.

An alias for `x86_64-unknown-linux-gnu`, the default target for Linux.

An alias for `aarch64-apple-darwin`, the default target for macOS.

A 64-bit x86 Windows target.

A 32-bit x86 Windows target.

An x86 Linux target. Equivalent to `x86_64-manylinux_2_17`.

An ARM-based macOS target, as seen on Apple Silicon devices

By default, assumes the least-recent, non-EOL macOS version (12.0), but respects the `MACOSX_DEPLOYMENT_TARGET` environment variable if set.

An x86 macOS target.

By default, assumes the least-recent, non-EOL macOS version (12.0), but respects the `MACOSX_DEPLOYMENT_TARGET` environment variable if set.

An ARM64 Linux target. Equivalent to `aarch64-manylinux_2_17`.

An ARM64 Linux target.

An `x86_64` Linux target.

An `x86_64` target for the `manylinux2014` platform. Equivalent to `x86_64-manylinux_2_17`.

An `x86_64` target for the `manylinux_2_17` platform.

An `x86_64` target for the `manylinux_2_28` platform.

An `x86_64` target for the `manylinux_2_31` platform.

An `x86_64` target for the `manylinux_2_32` platform.

An `x86_64` target for the `manylinux_2_33` platform.

An `x86_64` target for the `manylinux_2_34` platform.

An `x86_64` target for the `manylinux_2_35` platform.

An `x86_64` target for the `manylinux_2_36` platform.

An `x86_64` target for the `manylinux_2_37` platform.

An `x86_64` target for the `manylinux_2_38` platform.

An `x86_64` target for the `manylinux_2_39` platform.

An `x86_64` target for the `manylinux_2_40` platform.

An ARM64 target for the `manylinux2014` platform. Equivalent to `aarch64-manylinux_2_17`.

An ARM64 target for the `manylinux_2_17` platform.

An ARM64 target for the `manylinux_2_28` platform.

An ARM64 target for the `manylinux_2_31` platform.

An ARM64 target for the `manylinux_2_32` platform.

An ARM64 target for the `manylinux_2_33` platform.

An ARM64 target for the `manylinux_2_34` platform.

An ARM64 target for the `manylinux_2_35` platform.

An ARM64 target for the `manylinux_2_36` platform.

An ARM64 target for the `manylinux_2_37` platform.

An ARM64 target for the `manylinux_2_38` platform.

An ARM64 target for the `manylinux_2_39` platform.

An ARM64 target for the `manylinux_2_40` platform.

Packages to exclude as workspace members. If a package matches both `members` and `exclude`, it will be excluded.

Supports both globs and explicit paths.

For more information on the glob syntax, refer to the [`glob` documentation](https://docs.rs/glob/latest/glob/struct.Pattern.html).

Packages to include as workspace members.

Supports both globs and explicit paths.

For more information on the glob syntax, refer to the [`glob` documentation](https://docs.rs/glob/latest/glob/struct.Pattern.html).

A host or host-port pair.

Try trusted publishing when we're already in GitHub Actions, continue if that fails.

Provide a JSON object that satisfies the schema "CombinedOptions". Here are the required top‑level fields: none (all optional). Return only the valid JSON object.