Clean up dependency pins and update all packages#91109
Clean up dependency pins and update all packages#91109fluttergithubbot merged 1 commit intoflutter:masterfrom
Conversation
|
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. |
There was a problem hiding this comment.
this got reverted? did you change this, or was it flutter update-packages?
There was a problem hiding this comment.
odd, i did that by accident at one point but i thought i'd fixed it... checking, one sec
There was a problem hiding this comment.
i think i forgot to rerun the tool after updating that particular pin, heh. will push new update.
aeacdbe to
d75cc83
Compare
christopherfujino
left a comment
There was a problem hiding this comment.
LGTM, pending CI passing
|
This can land on red as soon as the bots are happy, it is intended to fix the tree redness. |
|
Will "waiting for tree to go green" work here? This is the cause for the redness... |
|
Linux_web_tests all failed on timeouts. I'm rerunning "_0" as a test to see if rerunning helps. |
|
This pull request is not suitable for automatic merging in its current state.
|
|
The Linux_web_tests_0 is running long and will likely timeout. Is there something in this PR that could be leading to that? |
306a2b3 to
7a52f28
Compare
unfortunately not, see #81568 |
|
It's failing again on the signature even after the force push...? |
|
Yeah I hadn't finished updating it. This version should be good though! |
There was a problem hiding this comment.
Now that we're pinning this exactly, I'm guessing we should let the Flutter Material team know? @pennzht
There was a problem hiding this comment.
I don't know that we ever run this command with asserts. Perhaps this should be an explicit integration test?
There was a problem hiding this comment.
Yeah, that makes sense. I did an assert because it's private but that's dumb, I should just make it public and test it.
a5aead2 to
5f47996
Compare
Fixes #91108