Recordspypipydantic-settings
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.14.2
windows · python@3.10
4 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| pydantic | 2.13.4 | PASS All observations passed | contract passed | 8 project-days |
| pydantic | 2.13.5 | PASS All observations passed | contract passed | 1 project-day |
| python-dotenv | 1.2.2 | PASS All observations passed | contract passed | 7 project-days |
| python-dotenv | 1.2.3 | PASS All observations passed | contract passed | 1 project-day |
| typing-inspection | 0.4.2 | PASS All observations passed | contract passed | 7 project-days |
| typing-inspection | 0.4.4 | PASS All observations passed | contract passed | 1 project-day |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.15.0 | 2.14.2 |
|---|---|---|
| pydantic | 2.13.5 | 2.13.5 |
| python-dotenv | 1.2.3 | 1.2.3 |
| typing-inspection | 0.4.4 | 0.4.4 |
Moved: 0 · 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.