adding tool.uv.environments results in sync --locked always failing

[garymm]

Hi. Thank you for uv! It's awesome.
I'm not sure if I'm doing something wrong, but I can't get sync --locked to work when specifying tool.uv.environments in my pyproject.toml. Example:

#:schema https://json.schemastore.org/pyproject.json
[build-system]
requires = ["setuptools"]
build-backend = "setuptools.build_meta"

[project]
name = "demo"
requires-python = ">=3.11,<3.12"
# https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#static-vs-dynamic-metadata
dynamic = ["version"]
dependencies = [
    "pytest>=8.3.3",
]

[tool.uv]
environments = [
    "sys_platform == 'darwin' and platform_machine == 'arm64' and python_version>='3.11' and python_version<'3.12'",
    "sys_platform == 'linux' and platform_machine == 'aarch64' and python_version>='3.11' and python_version<'3.12'",
    "sys_platform == 'linux' and platform_machine == 'x86_64' and python_version>='3.11' and python_version<'3.12'",
]

➜ uv --version
uv 0.4.17
➜ uv lock
Using CPython 3.11.9
Resolved 5 packages in 682ms
➜ uv sync --locked
Using CPython 3.11.9
Creating virtual environment at: .venv
Resolved 5 packages in 4ms
error: The lockfile at `uv.lock` needs to be updated, but `--locked` was provided. To update the lockfile, run `uv lock`.

[zanieb]

Weird, thanks.

cc @BurntSushi / @charliermarsh

[charliermarsh]

Thanks, I'll fix this tomorrow!

[charliermarsh]

(I see the issue.)