I don't know what the solution to this is, but I think it's worth starting a discussion to see if there's a way to improve things.

Currently there are some packages inside the Dart SDK repository that ship both with Dart and are also published to pub and used by Flutter - for example DDS and DWDS.

Today, the version of these components inside the Dart SDK and the Flutter SDK can be different versions if changes are made in the Dart SDK, but they are not released to pub and rolled into Flutter. For example the recent DAP bug (dart-lang/sdk#54087) is an issue in the latest Flutter SDK but only for Flutter projects (which use flutter debug_adapter) and not for Dart projects (which use dart debug_adapter) from the same SDK version.

To avoid this, we need to ensure when a release is being made that any local packages in the SDK have been published to Pub and rolled into Flutter. Doing this manually is error prone - especially as Pub releases aren't pushed on every change (because that would be a big overhead).

One possible improvement would be to have a script that checks (when preparing a Flutter release) that the version in the pubspec.yaml for a package that lives in the Dart SDK repository matches the one in Flutter's pubspec.yaml (we could also check against Pub, but if Dart+Flutter match it's certain the package was published to Pub).

This would rely on the version being bumped in pubspec.yaml in the package in the SDK with changes, but I suspect that's something much less likely to be wrong than forgetting to do a Pub release prior to a branch.

@devoncarew @jacob314