Yeah, that's my assumption as well. It would explain why there's no mention of it in breaking changes, and why being specific about the generics in `SinonStub` fixes the error.
Makes me wonder what other unsoundness the compiler isn't catching.
You have it backwards, the error in question is complaining that `any[]` does not satisfy the tuple type.
Minimal repro:
The error matches yours: From poking the playground, `any[]` hasn't been assignable to tuples since at least v3.3.3My guess is that the compiler got smarter around reasoning about your `SinonSub` generic and is now forcing you to deal with lingering unsoundness.