dart format --language-version=3.7 vs sdk: '>=3.7.0 <4.0.0'

[dcharkes]

I'm somewhat confused around how the formatter versions work. The command line --language-version seems to not agree 100% with the language version in the pubspec.

I'm seeing a difference between

$ dart format --language-version=3.7 .

and

$ dart format .

My pubspec contains:

environment:
  sdk: '>=3.7.0 <4.0.0'

The diff

diff --git a/pkgs/native_assets_cli/example/build/native_add_library/hook/build.dart b/pkgs/native_assets_cli/example/build/native_add_library/hook/build.dart
index b8ddfd95..aa0b20e7 100644
--- a/pkgs/native_assets_cli/example/build/native_add_library/hook/build.dart
+++ b/pkgs/native_assets_cli/example/build/native_add_library/hook/build.dart
@@ -17,9 +17,10 @@ void main(List<String> args) async {
     await cbuilder.run(
       input: input,
       output: output,
-      logger: Logger('')
-        ..level = Level.ALL
-        ..onRecord.listen((record) => print(record.message)),
+      logger:
+          Logger('')
+            ..level = Level.ALL
+            ..onRecord.listen((record) => print(record.message)),
     );
   });
 }

My understanding was that the formatter is per language version. So, any future changes in the formatter will not change the formatting until the language version is bumped in the pubspec. However, on the GitHub CI dart format . seems to want to have the files formatted as dart format --language-version=3.7 . locally, which means the CI becomes red.

Local Dart version:

$ dart --version
Dart SDK version: 3.8.0-24.0.dev (dev)

@munificent How are breaking changes to the formatter handled?

[dcharkes]

Ah, there was an old package_config.json:

    {
      "name": "native_add_library",
      "rootUri": "../",
      "packageUri": "lib/",
      "languageVersion": "3.3"
    }

[munificent]

Ah, there was an old package_config.json:

Yeah, this is a really really annoying failure mode. We aren't sure the best way to deal with it yet. See #1597.