)]}'
{
  "commit": "5dec261948add3c1cc720f0f47c7d7b499298201",
  "tree": "9c1f3d49d255d6ea2cd595a2f56b1093ccc35e3b",
  "parents": [
    "0467dfc43458e03624d93dba35e819a462f2def9"
  ],
  "author": {
    "name": "Paul Berry",
    "email": "paulberry@google.com",
    "time": "Thu May 29 21:53:01 2025 -0700"
  },
  "committer": {
    "name": "Commit Queue",
    "email": "dart-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Thu May 29 21:53:01 2025 -0700"
  },
  "message": "Fix test group name for sound flow analysis.\n\nI accidentally called the test group \"Sound null safety\", which is a\nrelated concept, but not the same thing.\n\nSound null safety is a compilation mode in which no legacy code is\nallowed, and so it is sound to assume that an expression with a\nnon-nullable type cannot evaluate to `null`. It has been the only\nallowed way to compile Dart programs for some time.\n\nSound flow analysis, on the other hand, is a set of improvements to\nflow analysis which are possible now that all Dart programs are now\ncompiled in sound null safety mode. It is a language-versioned feature\nthat is enabled in Dart 3.9.\n\nChange-Id: Ib13d28be7fecea6d0e931b33d6643afab2349629\nReviewed-on: https://dart-review.googlesource.com/c/sdk/+/432004\nAuto-Submit: Paul Berry \u003cpaulberry@google.com\u003e\nReviewed-by: Konstantin Shcheglov \u003cscheglov@google.com\u003e\nCommit-Queue: Konstantin Shcheglov \u003cscheglov@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c284f6ab3684476b8ec07961b25cd802ab95f755",
      "old_mode": 33188,
      "old_path": "pkg/_fe_analyzer_shared/test/flow_analysis/flow_analysis_test.dart",
      "new_id": "67e900fee4bd773baf31e3ea011ce5b09911e502",
      "new_mode": 33188,
      "new_path": "pkg/_fe_analyzer_shared/test/flow_analysis/flow_analysis_test.dart"
    }
  ]
}