pythonp1c2u/jsonschema-path #156Not a task: already works

Support `referencing` v0.36.0

envgap__p1c2u__jsonschema-path-156

Original GitHub issue ↗Dated source checkout ↗Opened 2025-01-23

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: cff02ef363d97fb2bebdc734f88b143db13957b6
Manifest: pyproject.toml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

p1c2u/jsonschema-path #156 · read the original issue

Just like #98 said, the upper limit pinning for a `referencing` minor release version is causing problems again. This time it's because `referencing` released v0.36.0 last week, so dependency resolvers (like `poetry`) end up downgrading a bunch of packages until `jsonschema-path` is no longer needed (e.g. by a very old version of `openapi-spec-validator`). Would it make sense to change the pin to a major release, i.e. `<1.0.0`?

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

[]