pythonpython-openapi/openapi-spec-validator #486Not a task: already works

Upgrading openapi-spec-validator 0.7.2 → 0.8.4 downgrades jsonschema 4.26.2 → 4.24.1

envgap__python-openapi__openapi-spec-validator-486

Original GitHub issue ↗Dated source checkout ↗Opened 2026-03-06

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: cca400fbe29ebaea5c3b3e7db04548db260690ea
Manifest: pyproject.toml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

python-openapi/openapi-spec-validator #486 · read the original issue

While upgrading openapi-spec-validator from 0.7.2 to 0.8.4, I noticed that jsonschema is downgraded from 4.26.2 to 4.24.1. This downgrade is introduced by this [commit](https://github.com/python-openapi/openapi-spec-validator/commit/10706ccbe2c519893cfb33b05b5c7dcf6a9b8062).

I noticed that the package is constrained to 4.24.0-4.25.0, as confirmed in `pyproject.toml`.

This creates a regression for us because updating openapi-spec-validator forces a downgrade of jsonschema.

**Steps to reproduce**
Install openapi-spec-validator==0.7.2 → jsonschema resolves to 4.26.2
Upgrade to openapi-spec-validator==0.8.4 → jsonschema resolves to 4.24.1

**Expected**
Upgrading openapi-spec-validator should not force a downgrade of jsonschema (or should allow jsonschema>=4.26.2).

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]