Recordspypipydanticfailure issue
Failure signature
PROJECT_TEST exit 1 ERROR ×2
E AssertionError: assert [<str>] == [<str>] · E · E At index 0 diff: <str> != <str> · E Use -v to get more diff
Evidence quality: complete · python/pytest · test-runner-diagnostic · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:80523b71cbb5…
pydantic.BaseModel pydantic.Field pydantic.ValidationError
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 2.13.5 not measured
- 2.13.4 FAIL
- 2.10.6 PASS 1 passing observations
- 2.8.2 PASS 1 passing observations
Where it reproduced
- os=windows · runtime=python@3.10 ×2 2026-09-01 → 2026-09-01
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 2.10.6 → first failing release 2.13.4
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 2.13.5 | 2.13.4 | 2.8.2 |
|---|---|---|---|
| pydantic-core | 2.46.5 | 2.46.4 | 2.20.1 |
| annotated-types | 0.8.0 | 0.8.0 | 0.8.0 |
| typing-extensions | 4.16.0 | 4.16.0 | 4.16.0 |
| typing-inspection | 0.4.4 | 0.4.4 | — |
Moved: 1 · unchanged at every release: 3
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 1
- No resolved dependency tree for 2.10.6 or for 2.13.4, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- pydantic 2.13.4: pydantic This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWpydantic MIT-0 · 2026-09-05
- pydantic 2.13.4: model_validator This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWpydantic.model_validator MIT-0 · 2026-09-01
- pydantic 2.13.4: Validate and sanitize field values across field_validator modes before, after, wrap, and plain with ValidationInfo sibling field access in Pydantic 2.13.4 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWpydantic.BaseModelpydantic.ValidationErrorpydantic.ValidationInfopydantic.field_validatorpython MIT-0 · 2026-08-28