@jonahwilliams do you know why isolate deps would be disagreeing with themselves? I just ran ./bin/flutter update-packages --force-upgrade. 😁

@srawlins I'm not sure why specifically, but I do recall someone else having an issue with the isolate dep.

apparently the analyzer had a dependency on isolate until recently

Anything I can do or like... not?

cc @devoncarew

Hmm, package:analyzer removed its dep (which was I believe in 1.1.0). That should make version resolution easier. I'd look to see which packages here still have a dep on isolate.

Only two direct dependencies

$ find . -name pubspec.yaml -exec grep isolate {} \; -print
  isolate: 2.0.0
./examples/stocks/pubspec.yaml
  isolate: 2.0.0 # THIS LINE IS AUTOGENERATED - TO UPDATE USE "flutter update-packages --force-upgrade"
./dev/benchmarks/microbenchmarks/pubspec.yaml

OK I think I found something. This bumps the version of test to 0.12.37, which has a transitive dependency on isolate ^1.1.0.

The test package depends on the analyzer package. The latest analyzer, 0.31.1 depends on isolate >=0.2.2 <2.0.0.

Opened a bug for @jonahwilliams or... whomever. #17473.

@srawlins, I'm going to look at changing how we depend on package:analyzer (after my analysis PR we no longer need the version from the sdk). That may indirectly help this PR out...

@srawlins, you should be good to go. You'll have some merge conflicts :) You may want to re-apply the mockito change in a new PR.

lol yeah its not easy recovering from these merges. I'll probably open a new PR in a bit.