)]}'
{
  "commit": "f58d5768f1fd0df9f71aa6ae5f63645e2637c31f",
  "tree": "38e44ec0004c436aec48300e1ad781ed065c37f2",
  "parents": [
    "7af1efe4b264af96291c1e34b331a8f3f65a3775"
  ],
  "author": {
    "name": "Omar Abdelsalam",
    "email": "oe7836196@gmail.com",
    "time": "Mon Oct 26 20:11:08 2026 +0300"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Oct 26 10:11:08 2026 -0700"
  },
  "message": "Pin swift-crypto for the Swift CI matrix (#9412)\n\nThe Swift test job pulls in grpc-swift-2 -\u003e grpc-swift-nio-transport -\u003e\nswift-nio-ssl -\u003e swift-crypto, and this package ships no Package.resolved,\nso that whole graph is resolved afresh on every run. On 2026-10-15 it\nresolved swift-crypto 5.0.1 (released three days earlier) and \"Test Swift\nLinux (6.2)\" turned red before a single line of FlatBuffers\u0027 Swift code was\ncompiled:\n\n  Sources/Crypto/HPKE/Ciphersuite/HPKE-AEAD.swift:27:6: error: unknown\n  attribute \u0027nonexhaustive\u0027\n\n5.x declares swift-tools-version 6.2, which is why only the 6.2 job selects\nit; the 6.0 and 6.1 jobs prune it and keep building. The 6.2.x toolchains\nthen reject the `@nonexhaustive` that 5.x uses, a combination swift-crypto\ndoes not exercise because it builds on nightly.\n\nRestrict the test-only graph to 4.0.0 ..\u003c 4.4.0, which resolves to 4.3.0:\nthe last 4.x release that declares swift-tools-version 6.0 and so builds\nwith every toolchain in the matrix. 4.4+ asks for 6.1 and would break the 6.0\njob, and the whole 4.x line is free of `@nonexhaustive`.\n\nCo-authored-by: Derek Bailey \u003cderekbailey@google.com\u003e",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "413990384ffd2976c4e7df1cd7a4fec34e7ff722",
      "old_mode": 33188,
      "old_path": "Package.swift",
      "new_id": "6c1b808c2b457c8d55a2c95d5f179325d4628098",
      "new_mode": 33188,
      "new_path": "Package.swift"
    }
  ]
}