Recordspypipydantic2.8.2pydantic.StringConstraints
Change the conditions
Current conditions
pydantic.StringConstraints @2.8.2windows · x64 · python 3.10 · pip 26
5 of 5 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 5 / 5
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-18
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| pydantic-core | 2.20.1 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| annotated-types | 0.8.0 | PASS All observations passed | contract passed | 1 project-day |
| typing-extensions | 4.16.0 | 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.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.