[flutter_tools] Manually roll pub deps#119286
[flutter_tools] Manually roll pub deps#119286christopherfujino wants to merge 2 commits intoflutter:masterfrom
Conversation
flutter-dashboard
bot
added
the
c: contributor-productivity
christopherfujino
added
the
autosubmit
auto-submit
bot
removed
the
autosubmit
|
auto label is removed for flutter/flutter, pr: 119286, due to - The status or check suite Mac tool_integration_tests_4_4 has failed. Please fix the issues identified (or deflake) before re-applying this label. |
|
restarting two presubmit checks that failed for infra reasons |
| dds_service_extensions: 1.3.1 # THIS LINE IS AUTOGENERATED - TO UPDATE USE "flutter update-packages --force-upgrade" | ||
| devtools_shared: 2.20.1 # THIS LINE IS AUTOGENERATED - TO UPDATE USE "flutter update-packages --force-upgrade" | ||
| dds_service_extensions: 1.3.2 # THIS LINE IS AUTOGENERATED - TO UPDATE USE "flutter update-packages --force-upgrade" | ||
| devtools_shared: 2.21.0-dev.0 # THIS LINE IS AUTOGENERATED - TO UPDATE USE "flutter update-packages --force-upgrade" |
There was a problem hiding this comment.
@christopherfujino do you know why this went to -dev? I just ran this command locally because there's a new DDS today that I'd like (#119340 is just a copy of this but run more recently, including the new DDS) and I noticed this there too.
I couldn't see any packages that need the dev version - do we just always take the latest, whether it's dev or not? (and if so, is that intended or accidental?)
There was a problem hiding this comment.
do we just always take the latest, whether it's dev or not?
I believe that yes, this is the algorithm pub uses.
|
Superceded by #119340 |
3 participants
This notably increases vm_service from 9.4.0 -> 10.1.0