pinecrew / pined-django / 33506593997

95%

push

github

repo: lower the pydantic floors to where they actually are

The declared floors were the versions that happened to be installed, not
versions anything had been run against. Bisected instead, one release at a
time, running the suite at each.

`pydantic>=2.13.4` → `>=2.11.4` for `pydantic-field`. Not the 2.10.4
`json-schema-to-pydantic` asks for: it builds its model with
`create_model(__base__=..., __config__=...)`, and pydantic refused that pairing
until 2.11.4 — so the whole suite fails on 2.11.3 with 35 errors, none of them
in code of ours.

`pydantic>=2.10` for `settings`, which is what this package's own code needs.
2.10 is where pydantic learned to resolve a PEP 695 `type` alias; on 2.9 the
`UnsetType` inside `Unset[T]` is an unknown type and no settings model builds
at all. Verified with the settings tests that do not need a database — the
ones that do go through the test app's migration chain, which drags
`json-schema-to-pydantic` in and hides the difference.

`pydantic-settings>=2.15.0` → `>=2.0.3`, which is the oldest 2.x there is and
passes the whole suite. Nothing here reaches for anything newer than
`SettingsConfigDict` had on day one.

`test (lowest direct)` is what makes these more than a claim, and it resolves
exactly them: pydantic 2.11.4, pydantic-settings 2.0.3, json-schema-to-pydantic
0.4.11, dj-database-url 3.1.2, django 5.2. 287 passed there and at the top of
the ranges both.

229 of 250 branches covered (91.6%)

Branch coverage included in aggregate %.

1297 of 1360 relevant lines covered (95.37%)

0.95 hits per line