I lowered the version to 1.24.0 (stable). Will land on green.

For our work on bringing new dart frontend to flutter #10841 it is critical for us to have more or less latest dart in flutter engine as there are changes being made to dart vm to accommodate new frontend work.
With that in mind - is lowering to 1.24-stable temporary thing to troubleshoot #10650 or we need to come up with some mechanism of having parallel build of flutter engine/flutter tools that lives on more recent versions of dart?

@aam this isn't the Dart SDK version of the embedder (the engine) -- this is the Dart SDK version of the flutter tool (which is being upped from 1.24.0-dev.6.7 to 1.24.0).

It's admittedly unfortunate and confusing that the two aren't in sync.

We (rather trivially) could build our own Dart SDK on our bots and download it from the flutter_infra GCE bucket and always have the flutter/flutter version use the flutter/engine's exact Dart revision. We just haven't done it.

Oops, got you, thanks!
By the way, you can use 'hash/65a5707189dec6c5e0174cbc821acfb90f0c9b3f' syntax in bin/internal/dart-sdk.version to reference particular bleeding edge of dart.
Also, with dart frontend support rolling out to flutter, version of dart sdk used by the flutter tools will have to [closely] match version of dart sdk used in the engine since kernel(parse tree) binaries produced on the workstation have to be compatible with what kernel binary reader on the device expects.

We should coordinate that with the team in Google that rolls the Dart SDK internally, since we want to make sure we don't put ourselves in a situation where we can't roll Flutter into Google because it depends on a Dart SDK version that's too far ahead of the internal SDK version.

/cc @keertip @srawlins

In short term, it will take some time for us to iron all kinks out flutter-with-new-frontend configuration. While we do that, new frontend functionality in flutter will be "hidden" behind configuration option (flutter run --is-kernel-mode, for example). During that phase, there is no need for everybody to have flutter tools and flutter engine on the same revision - only folks who decide to run with --is-kernel-mode have to do that, and they can accomplish this by manually updating dart-sdk.version to hash/..., that matches engine/src/flutter/DEPS dart_revision.
Hopefully by the time frontend integration with flutter is tested and verified, there will be no need to stay on bleeding edge of dart to pick up dart vm fixes for frontend, so we can go back to using dev channel versions.
Generally speaking, though, there will be [small?] risk in in rolling engine's dart dependency forward while leaving flutter tools's dart-sdk in place in case there are some changes to kernel format.

@a-siva