@DanTup @bkonyi @derekxu16 I think this is unblocked now, right?

-  test_api: 0.6.1
-  test_core: 0.5.9
+  test_api: 0.7.0
+  test_core: 0.6.0

-  vm_service: 13.0.0
+  vm_service: 14.0.0

@DanTup @bkonyi @derekxu16 I think this is unblocked now, right?

Yes, it is safe to update package:vm_service.

Maybe we'll need to roll devtools in flutter/tests?

| Because every version of integration_test from sdk depends on vm_service 14.0.0 and devtools_app depends on vm_service ^13.0.0, integration_test from sdk is forbidden.
| So, because devtools_app depends on integration_test from sdk, version solving failed.
ERROR: Could not run "flutter pub get" in packages/devtools_app, which was specified as an update directory.

https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20customer_testing/68365/overview

I'll look to update flutter/tests....

Maybe we'll need to roll devtools in flutter/tests?

| Because every version of integration_test from sdk depends on vm_service 14.0.0 and devtools_app depends on vm_service ^13.0.0, integration_test from sdk is forbidden.
| So, because devtools_app depends on integration_test from sdk, version solving failed.
ERROR: Could not run "flutter pub get" in packages/devtools_app, which was specified as an update directory.

https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20customer_testing/68365/overview

I'll look to update flutter/tests....

Oh actually, devtools hasn't been updated yet. @derekxu16 would you be able to update vm_service in devtools_app, since I think you are also blocked on this?

Oh actually, devtools hasn't been updated yet. @derekxu16 would you be able to update vm_service in devtools_app, since I think you are also blocked on this?

Unfortunately, there's a cycle here. package:devtools_app cannot be updated to accept package:vm_service 14.0.0 until package:integration_test accepts it.

From https://github.com/flutter/devtools/actions/runs/7450073310/job/20268216240:

Because devtools_test depends on integration_test from sdk which depends on vm_service 13.0.0, vm_service 13.0.0 is required.
So, because devtools_test depends on vm_service ^14.0.0, version solving failed.

package:devtools_app cannot be updated to accept package:vm_service 14.0.0 until package:integration_test accepts it.

Could DevTools be updated to support 13 + 14? (I don't know how breaking the changes are, so I don't know if that'll work). Otherwise, could DevTools be excluded from customer tests to land this, then updated, then re-added?

Could DevTools be updated to support 13 + 14? (I don't know how breaking the changes are, so I don't know if that'll work). Otherwise, could DevTools be excluded from customer tests to land this, then updated, then re-added?

Following the second suggestion would be ideal. A lot of special checks would have to be added to convert between ints and DateTimes to make DevTools support both package:vm_service v13 and v14. Would it be possible to follow the second suggestion, @christopherfujino?

Could DevTools be updated to support 13 + 14? (I don't know how breaking the changes are, so I don't know if that'll work). Otherwise, could DevTools be excluded from customer tests to land this, then updated, then re-added?

Following the second suggestion would be ideal. A lot of special checks would have to be added to convert between ints and DateTimes to make DevTools support both package:vm_service v13 and v14. Would it be possible to follow the second suggestion, @christopherfujino?

This is fine with me, as long as it's good with @kenzieschmoll. I just want to make sure we don't end up trying to roll an incompatible version of devtools into flutter/flutter.

@derekxu16 has a draft PR to update DevTools to vm_service 14: flutter/devtools#6953. Derek can you give an update on this? If we disable the customer tests, then the DevTools CI will start failing shortly after this PR lands. So we will need to migrate DevTools to 14 either way.

@derekxu16 has a draft PR to update DevTools to vm_service 14: flutter/devtools#6953. Derek can you give an update on this?

That PR is ready for review.

I reviewed @derekxu16's DevTools PR to bump to vm_service 14. Let's follow the plan suggested above:

1. disable the DevTools flutter customer tests for now
2. land this PR
3. once the DevTools CI picks up this version of Flutter and the build goes red, Derek can land his DevTools PR to bump to vm_service 14 and fix the build
4. re-enable the DevTools flutter customer tests with the hash of Derek's DevTools PR

Just wondering, what is the status of this?

Just wondering, what is the status of this?

I'm gonna pick this up again next week--I'm pretty swamped right now.

@christopherfujino @bkonyi what's the current status of VM service 13/14? I was just trying to use DDS as a path dependency in Flutter and noticed that Flutter's vm_service dependency has been bumped to v14 here, but DDS in the SDK repo was put back to down to 13.

Was it an error that Flutter went up to 14? If not, when will DDS also use 14?

The vm_service constraint of DDS in the SDK was accidentally set back to ^13.0.0. I'm working on publishing a new version of DDS that accepts vm_service: ^14.0.0.

Published.

https://pub.dev/packages/dds/versions/3.2.0