Downstream testing for language pacakge managers, it's buildable but perhaps not fundable?

https://nesbitt.io/2026/03/01/downstream-testing.html

Downstream Testing

Most library maintainers have no way to test against their dependents before releasing.

Andrew Nesbitt

@andrewnez there’s an interesting intersection with resolution policy here.

Because bundler/rubygems always try to resolve every dep to a single version, a feedback loop occurs where breakage upstream quickly attracts patches that mostly re-level the ecosystem.

But in systems allowing multiple versions to be resolved, that feedback loop is largely absent and so the spread of versions in use is more heavy tailed.

@andrewnez I also just remembered that in my time at Shopify I wanted to build a kind of progressive rollout system for new versions. Working from low-impact repos up to The Monolith. Integrated with the ShipIt deployment tool as well to get traffic control. Got laid off before I could pitch it properly 🤷
@jacques @andrewnez Oh, man, same. I worked in Resiliency and tried to get Dev Infra on board with this. I got cut before I could get far enough, though.