It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@jakemac53

it looks like we cant update our version of test because we have customer tests that dont version solve. I'm not sure what to do here

it looks like we cant update our version of test because we have customer tests that dont version solve. I'm not sure what to do here

In general, we have to update the customer repos before landing changes that would break them. So, I guess in this case that would bean loosening the constraints in the customer pubspecs?

It looks like https://github.com/PhilipsHue/flutter_reactive_ble/blob/master/pubspec.yaml is already up to date, but a new version needs to be rolled in. This can't be done atomically so I'll have to disable and then re-enable

provider (https://github.com/rrousselGit/provider/blob/master/pubspec.yaml ) has also been updated and will require a similar disable then re-enable to roll in

test-exempt: dependency upgrade.

We really should make an automated bot to roll these.

This one was definitely not gonna roll in automatically 😓

Yeah, but an automated roller would let us know as soon as that kind of problem came around, instead of us finding out at inconvenient times.

Trying again in #83367