Debian Patches
Status for ormar/0.24.0-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Fix-failing-tests.patch | Fix failing tests | Edward Betts <edward@4angle.com> | no | 2025-12-29 | ||
| pydantic-2.13-defer-build.patch | fix: support pydantic 2.13 by invalidating cached model schema (#1694) * fix: support pydantic 2.13 by invalidating cached model schema Pydantic 2.13 changed how `TypeAdapter(Annotated[T, FieldInfo(...)])` — FastAPI's response-serializer pattern — resolves nested schemas: it now uses the cached child snapshot instead of walking the live model. As a result, reverse-relation fields that ormar's metaclass adds to related models in `expand_reverse_relationships` were invisible from nested dumps under pydantic 2.13. Invalidate the parent's cached schema by setting `__pydantic_complete__ = False` at the end of the ormar metaclass, so the next access recompiles afresh without the stale snapshot. Make the wrap-serializer fallbacks (forward + reverse relation) defensive against the broader value types (QuerysetProxy, dead weakproxy) that pydantic 2.13 now dispatches them with. Relax the pydantic upper bound so 2.13.x is accepted. * build: pin pydantic below 2.14 due to internals dependency Ormar relies on pydantic internals, so the upper bound is capped at <2.14 and must be bumped manually after verifying compatibility with each new release. Refreshes the lock content-hash; resolved versions are unchanged (pydantic stays at 2.12.5). |
collerek <collerek@gmail.com> | yes | debian upstream | backport, https://github.com/ormar-orm/ormar/commit/12718030c9e43708083f55f0f63f4cd048e5651a | 2026-05-25 |