)]}'
{
  "commit": "f06613a75d1022de09fe2045de51af11b2eb798b",
  "tree": "744d97d3b9fa5e1677199f736cf1b563ae50e0f3",
  "parents": [
    "8c5b4182b3ed456169e356a5da913a8ad8a5fe1b"
  ],
  "author": {
    "name": "Thomas Van Lenten",
    "email": "thomasvl@google.com",
    "time": "Mon Jun 08 13:58:22 2026 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Jun 08 14:00:05 2026 -0700"
  },
  "message": "json: Expand JSON parsing tests for custom-named and aliased enum values\n\nAdds test cases verifying the behaviors of custom enumval JSON strings\nand their raw enum name counterpart inputs under C++ JSON parsing:\n\n  - Confirms that aliased enum values (ARMOR_SABATON / ARMOR_SOLLERET)\n    serialize properly to their shared custom string (\"sabaton\") and\n    can round-trip back.\n  - Documents and proves that the JSON parser continues to accept raw\n    enum names (e.g., \"ARMOR_GREAT_HELM\") in addition to their custom\n    configured options on input.\n  - Verifies that a numeric custom string option (e.g., \"8\" for\n    ARMOR_HACHI_MAI_DO) serializes to string/parses back correctly,\n    and parses properly from custom/integer representations.\n\nPiperOrigin-RevId: 928755515\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d12569b1694298f5264803286b810434fc019a87",
      "old_mode": 33188,
      "old_path": "src/google/protobuf/json/json_enumval_custom_string.proto",
      "new_id": "0f72dc1b31e5b5248c6522601cd5769e6d0fcee4",
      "new_mode": 33188,
      "new_path": "src/google/protobuf/json/json_enumval_custom_string.proto"
    },
    {
      "type": "modify",
      "old_id": "525afb866def9a6a26295c5085f890e0d0a14650",
      "old_mode": 33188,
      "old_path": "src/google/protobuf/json/json_enumval_custom_string_test.cc",
      "new_id": "1aff3313b2b29df3e066050a37c741e62aad8ba8",
      "new_mode": 33188,
      "new_path": "src/google/protobuf/json/json_enumval_custom_string_test.cc"
    }
  ]
}