)]}'
{
  "commit": "eb40f1a6aefa58e5e234a063b02a6540dd16f5c3",
  "tree": "5dc0b6b2d8499b46bde5b9914fe055d39a05266b",
  "parents": [
    "63b3eff38ef1c216480147dd53b0e4365d55f269"
  ],
  "author": {
    "name": "Wilfred Hughes",
    "email": "me@wilfred.me.uk",
    "time": "Thu Mar 12 19:31:50 2026 +0000"
  },
  "committer": {
    "name": "Wilfred Hughes",
    "email": "me@wilfred.me.uk",
    "time": "Tue Mar 31 14:28:18 2026 +0100"
  },
  "message": "internal: Document when crate cycles can occur\n\nThis is legal when there are dev-dependencies, and rust-analyzer\nitself even does this. This causes spurious warnings in several cases,\nsuch as generating SCIP for rust-analyzer:\n\n```\n$ cargo run --bin rust-analyzer --release -- scip .\n2026-03-12T18:40:33.824092Z  WARN cyclic deps: cfg(Idx::\u003cCrateBuilder\u003e(21)) -\u003e cfg(Idx::\u003cCrateBuilder\u003e(21)), alternative path: cfg(Idx::\u003cCrateBuilder\u003e(21))\n```\n\nIn this case, the `cfg` crate enables its `tt` feature by depending\non itself in dev-dependencies.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "246c57edc2df30f00eb922b7a0763a571bec9ac4",
      "old_mode": 33188,
      "old_path": "crates/base-db/src/input.rs",
      "new_id": "4f32abafd77d1c90a311080e995b1ff09310439b",
      "new_mode": 33188,
      "new_path": "crates/base-db/src/input.rs"
    }
  ]
}