)]}'
{
  "commit": "fe5e42fbb4b3b616dfc074f1689e3f8b1d6e28df",
  "tree": "630d36ecbe293ae9130aae336f15669f9cd21887",
  "parents": [
    "f6c4c920c6551f1c40e0d04382a2ea1a8d052c91"
  ],
  "author": {
    "name": "虎鸣",
    "email": "hepin.p@alibaba-inc.com",
    "time": "Mon Jun 15 21:19:27 2026 +0800"
  },
  "committer": {
    "name": "虎鸣",
    "email": "hepin.p@alibaba-inc.com",
    "time": "Mon Jun 15 21:19:27 2026 +0800"
  },
  "message": "fix: remove explicit implicit passing in PathMatcher provide/apply\n\nMotivation:\nScala 2.13 reports ambiguous implicit values when `provide` and `apply`\nexplicitly pass `(ev)` to both the PathMatcher constructor and Matched\ncase class, creating two `ev: Tuple[L]` candidates in scope (method\nparameter and constructor val).\n\nModification:\nRemove explicit `(ev)` from constructor calls and Matched invocations\nin `provide` and `apply`, letting implicit resolution pick up `ev` from\nthe method\u0027s implicit parameter — matching the behavior of the original\n`[L: Tuple]` context bound pattern.\n\nResult:\nPathMatcher compiles cleanly on both Scala 2.13.18 and 3.3.8 with no\nambiguous implicit errors.\n\nTests:\n- sbt \"++ 2.13.18; http/compile\" passes\n- sbt \"++ 3.3.8; http/compile\" passes\n- sbt \"++ 2.13.18; http-tests/Test/testOnly ...PathDirectivesSpec\" 222 passed\n- sbt \"++ 2.13.18; http-tests/Test/testOnly ...EntityStreamingSpec\" 11 passed\n\nReferences:\nRefs #1067\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "af10a00f9c75022e9d8f8416180f5104651a63f9",
      "old_mode": 33188,
      "old_path": "http/src/main/scala/org/apache/pekko/http/scaladsl/server/PathMatcher.scala",
      "new_id": "147d22fd9e30783cdc80f4f2a286f508f0e3db73",
      "new_mode": 33188,
      "new_path": "http/src/main/scala/org/apache/pekko/http/scaladsl/server/PathMatcher.scala"
    }
  ]
}