)]}'
{
  "commit": "a69a28f40e14a5e6dd5aa62970a7c751b45b0e47",
  "tree": "894f03c99fc9bab9a4fcf74add317dfe0af5892f",
  "parents": [
    "9a33641a1269e83ca3f37958834016935c938e2a"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Tue Dec 02 12:40:01 2025 -0500"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Dec 02 22:49:03 2025 -0800"
  },
  "message": "Don\u0027t detect pre-C++11 in \u003copenssl/base.h\u003e\n\nWhen we first added bssl::UniquePtr, we added a __cplusplus version\ncheck to tolerate C++98 and C++03 consumers of our public headers, and\nonly giving them the C symbols.\n\nIt is now 2025. Since then, we\u0027ve added \u003copenssl/span.h\u003e and written\nC++17-requiring code in it, so C++11 and C++14 consumers of public\nheaders already broke. No longer try to bifurcate our consumer and\nimplementation C++ versions.\n\nUpdate-Note: C++ projects including BoringSSL headers now must be C++17\nor later, matching the requirement for building BoringSSL. C projects\nare unaffected. C++ projects that were previously building at C++98 or\nC++03 will need to update to a language version from sometime in the\nlast couple decades.\n\nChange-Id: I9e6ae1807398e5363ff71e0d2a83bfaa3f8bcbfc\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/84947\nCommit-Queue: Rudolf Polzer \u003crpolzer@google.com\u003e\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: Rudolf Polzer \u003crpolzer@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8707b541837c26c69454b00e2d2a2596c403433d",
      "old_mode": 33188,
      "old_path": "include/openssl/base.h",
      "new_id": "d942427dbe7dcfc85d483d6aac9ba9072ff37ef4",
      "new_mode": 33188,
      "new_path": "include/openssl/base.h"
    }
  ]
}