Clarified the reasoning behind a test dependency version pin
2184 sessions tracked this week across all builders
Determined why a test dependency is pinned to its current release—it reflects the upstream package's actual versioning, not arbitrary constraints.
Derived from this session's token and cost data. Not shown on the feed.
Comments