Recordspypisqlalchemy2.0.44sqlalchemy.String
Change the conditions
Current conditions
sqlalchemy.String @2.0.44windows 11 · x64 · python 3.10 · pip 26
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-18
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.0.44
windows · python@3.10
1 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| greenlet | 3.5.6 | CANDIDATE Correlated change; unproven combination | 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.0.52 | 2.0.51 | 2.0.44 | 2.0.43 |
|---|---|---|---|---|
| greenlet | 3.5.5 | 3.5.4 | 3.5.6 | 3.5.5 |
| typing-extensions | 4.16.0 | 4.16.0 | 4.16.0 | 4.16.0 |
Moved: 1 · unchanged at every release: 1
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.
Recent failure clusters
-
observed PROJECT_PROCESS Evidence gap ×1 2.0.44 os=windows · runtime=python@3.10Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-14 · Last seen: 2026-08-14