ansible lint 25.9.1 breaks uv sync, lock and add unless --prerelease=allow is added

[dh-seanmurphy]

Summary

ansible-lint 25.9.1 depends on an ansible-core version which depends on python 3.14. Python 3.14 is not released yet.

Almost certainly related to #4795

Issue Type

• Bug Report

OS / ENVIRONMENT

Not possible to run ansible-lint due to dependency problems.

Running in a container based on python 3.13.7.

• ansible installation method: uv
• ansible-lint installation method: uv

STEPS TO REPRODUCE

pyproject.toml

[project]
name = "ansible-lint-test"
version = "0.0.0"
dependencies = [
  "ansible-lint==25.9.1",
]

[tool.uv]
# Use the system interpreter provided in the docker image.
python-downloads = "never"

$ uv sync --locked
Using CPython 3.13.3 interpreter at: /usr/bin/python3
Removed virtual environment at: .venv
Creating virtual environment at: .venv
warning: No `requires-python` value found in the workspace. Defaulting to `>=3.13`.
  × No solution found when resolving dependencies for split (markers: python_full_version >= '3.14' and platform_python_implementation != 'PyPy'):
  ╰─▶ Because only ansible-core{python_full_version >= '3.14'}<2.20.0b1 is available and ansible-lint==25.9.1 depends on ansible-core{python_full_version
      >= '3.14'}>=2.20.0b1, we can conclude that ansible-lint==25.9.1 cannot be used.
      And because your project depends on ansible-lint==25.9.1, we can conclude that your project's requirements are unsatisfiable.

      hint: `ansible-core` was requested with a pre-release marker (e.g., ansible-core>=2.20.0b1), but pre-releases weren't enabled (try:
      `--prerelease=allow`)

      hint: While the active Python version is 3.13, the resolution failed for other Python versions supported by your project. Consider limiting your
      project's supported Python versions using `requires-python`

Desired Behavior

ansible-lint should be installed with dependencies which do not require the as yet unreleased python 3.14

Actual Behavior

ansible-lint installation fails.

[ssbarnea]

I think that this is a limitation of uv.lock files and you created the problem by prevent it from downloading python 3.14.

I will need more information to be able to reproduce the issue. AFAIK, installing ansible-lint==25.9.1 with either pip or uv works.

[dh-seanmurphy]

Thanks for this @ssbarnea - this is for some production tooling that we have; as python 3.14 is not released yet, we are not using it here.

It's a bit surprising that there is dependency on a unreleased python version.

[dbrennand]

Hi folks - Just hit a similar issue myself with my project. Bumping ansible-lint to 25.9.1 is causing the following error for me with uv:

home-ops/ansible on  main [!?] is 📦 v0.1.0 via 🐍 v3.13.7 
❯ uv sync --dev                                                 
  × No solution found when resolving dependencies for split (markers: python_full_version >= '3.14'):
  ╰─▶ Because only ansible-core{python_full_version >= '3.14'}<2.20.0b1 is available and ansible-lint==25.9.1 depends
      on ansible-core{python_full_version >= '3.14'}>=2.20.0b1, we can conclude that ansible-lint==25.9.1 cannot
      be used.
      And because ansible:dev depends on ansible-lint==25.9.1 and your project requires ansible:dev, we can conclude
      that your project's requirements are unsatisfiable.

      hint: `ansible-core` was requested with a pre-release marker (e.g., ansible-core>=2.20.0b1), but pre-releases
      weren't enabled (try: `--prerelease=allow`)

      hint: While the active Python version is 3.13, the resolution failed for other Python versions supported by
      your project. Consider limiting your project's supported Python versions using `requires-python`.

Can also see renovate is detecting issues when trying to update ansible-lint to 25.9.1: dbrennand/home-ops#273 (comment)

[sblask]

If there is a dependency on Python 3.14, this will certainly also break the pre-commit hook which now has a fixed requirement on Python 3.13? Can't tell though because for me it is failing because 3.13 can't be found: https://github.com/sblask/dotfiles/actions/runs/18194640163/job/51797555082?pr=977

[ssbarnea]

@sblask pre-commit-hook now defaults to py313 but you can override it if you want. Alternatively you can start adding pre-commit-uv to allow it to get newer pythons. You can find the reasoning for this on the PR.

Apparently this is an existing uv bug astral-sh/uv#2685 and I do not know how to bypass it.

I will try to explain the situation,

• current release of ansible-core does not support python 3.14
• first version of ansible-core that supports python 3.14 is 2.20.0b1 which is a pre-release
• to allow ansible-lint to be tested and install on all versions of python, including 3.14 we need to add a conditional dependency that requires the first version that can work with it
• we cannot put 2.20.0 there because uv resolved will fail due this not being available yet

Apparently current issue does not prevent installation using uv pip install or pip install, only uv add, uv sync and uv lock as the issue is related to the update of uv.lock file.

workaround 1

For allowing using of ansible-lint==25.9.1 on a uv based project by hardcoding the python version (not really desirable for most).

[project]
name = "1"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
requires-python = "==3.13.7"
dependencies = [
    "ansible-lint>=25.9.1",
]

workaround 2

Already suggested by uv hint, run uv lock --prerelease=allow and it will pass.

Does anyone have other suggestions?