)]}'
{
  "commit": "10edd16dcb2640a1a72adff06fcf0d424e44049d",
  "tree": "6ff2c611a194329afca1d1c177d244a760705a75",
  "parents": [
    "cc8a33aeaa37f681377c808d8307eb2ba9a6fef5",
    "b3a41f2385b46a6a29fe302ca6d1fe4190b18523"
  ],
  "author": {
    "name": "Jacob Pratt",
    "email": "jacob@jhpratt.dev",
    "time": "Tue Feb 24 22:51:40 2026 -0500"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Feb 24 22:51:40 2026 -0500"
  },
  "message": "Rollup merge of #152977 - arferreira:fix-extern-html-relative-depth, r\u003dnotriddle\n\nFix relative path handling for --extern-html-root-url\n\nWhen `--extern-html-root-url` receives a relative path (like `../`), rustdoc uses it as a literal prefix regardless of page depth. This works at depth 1 (`crate/index.html`) but breaks at depth 2+ (`crate/module/struct.Foo.html`) because the relative path doesn\u0027t account for the extra nesting.\n\nThis patch detects relative vs absolute URLs in the `Remote` branch of `url_parts` and prepends the necessary `../` segments based on the current page depth. Absolute URLs (`https://...`) and server-absolute paths (`/docs/...`) are unchanged.\n\nThis makes relative paths a viable option for `--extern-html-root-url`, which they weren\u0027t before.\n\nRelated to rust-lang/rust#152917, which exposed that relative paths weren\u0027t handled correctly.\n\ncc @eggyal\n",
  "tree_diff": []
}