)]}'
{
  "commit": "914c18ef2ea37888daaa0ca0d9eee84b2b3f1e00",
  "tree": "847f68cdad955e25a27535ea6cde9fe264909a0e",
  "parents": [
    "e2bd72e32ea49ad54fc4414173f8037148ab559e",
    "f8973b70ce31656cfd69bde2d20e6e8240448080"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Thu Jun 25 21:18:39 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Jun 25 21:18:39 2026 +0200"
  },
  "message": "Rollup merge of #158343 - obi1kenobi:pg/item-const-stability, r\u003dGuillaumeGomez\n\nInclude `Item::const_stability` info in rustdoc JSON.\n\nInclude a parallel `Item::const_stability` item in rustdoc JSON, sibling to `Item::stability` from rust-lang/rust#158230, intended for the same purpose of catching accidental breaking changes in the Rust standard library.\n\nI aimed to include `Item::const_stability` judiciously, when it would be genuinely useful without needlessly bloating the JSON. For example, if an item is already unstable, we do not duplicate the `Item::stability` value into `Item::const_stability` as the const-instability is clearly implied. I\u0027ve covered all such cases in the test suite and documented my reasoning inline.\n\nr? @GuillaumeGomez\n\n**AI disclosure:** This PR is the product of a combination of manual work and AI tools. I secured approval in advance from the designated reviewer. I stand behind the quality of the code I\u0027m submitting, and I vouch it\u0027s as good or better compared to if I had written every line by my own hand.\n\n(In particular, local AI review flagged several missing test cases, one of which caught a bug I would have missed otherwise.)\n",
  "tree_diff": []
}