VS Code extensions v3.138

72 views

Skip to first unread message

Danny Tuppeny

unread,

Jun 30, 2026, 9:25:12 AM (7 days ago) Jun 30

to flutter-...@googlegroups.com

Hi all,

New versions of the VS Code extensions have been published. Release notes are included below (and available online).

Editor

#6069: The LSP client has been updated to support LSP v3.18, allowing the Dart anlaysis server to take advantage of some new features and optimizations in future SDK releases.
#6085/#6087: Extension shutdown code now handles async dispose of services like the Analysis Server and allows them more time to shut down gracefully instead of abruptly terminating them.
#5176: ~~Enable delayOpenNotifications=true with LSP client vNext to prevent redundant didOpen/didClose notifications to server.~~ This change has been reverted as a possible cause of #6088 and will be re-enabled once that issue has been diagnosed/fixed.

Flutter

#6019/#6103: As previously announced, the Flutter Outline tree has been removed from the Flutter sidebar. The standard Outline is still available on the Explorer sidebar and the in-editor Flutter UI Guides preview is still available behind the dart.previewFlutterUiGuides setting.

Testing

#6091/#6093: When running a subset of a test suite using CodeLens links, the entire suite is no longer marked as Queued, which would cause the tests that didn’t run to appear as Skipped once the test run completed.

Dart Tooling Daemon

#6102/#6104: Active editor/location changes are no longer sent to DTD for non-main editors such as output panels or test result diffs.

Misc

#6065: When an SDK is not found, the “Locate SDK” button no longer fails to immediately reload using the newly-selected SDK, which caused the prompt to be shown repeatedly.
#6068: GitHub Actions scripts have been updated to handle new versions of Antigravity (Antigravity IDE).
#6097/#6106: GitHub Actions runs that cause “UNRESPONSIVE extension host” and trigger automatic CPU profiles are now captured and uploaded for investigation.

Upstream Issues

Some feature requests and fixes require new features and fixes in upstream projects like VS Code and LSP which use counts of 👍s on those issues to help gauge demand. The Dart-Code website now lists some of the most significant upstream issues with a description of the feature/fix they would enable. Please consider reviewing this list and adding your 👍 to any GitHub issues relevant to features you’d like to see!