)]}'
{
  "commit": "7b03f12461bbdf1e6b8d852fd0a79750292c9872",
  "tree": "100eabdcfa52062b70d6367320437a6ffd3e40df",
  "parents": [
    "02d6e2bca5699f35bb779589dd2f0767d27d32d5"
  ],
  "author": {
    "name": "Moraneus",
    "email": "48603901+moraneus@users.noreply.github.com",
    "time": "Thu May 21 19:08:50 2026"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu May 21 19:08:50 2026"
  },
  "message": "parser/unparser: emit valid CEL for doubles in scientific notation (#1326)\n\nstrconv.FormatFloat with \u0027g\u0027 and precision -1 emits scientific\nnotation for doubles of magnitude \u003c 1e-4 or \u003e\u003d 1e+21 (e.g. \"1e-05\",\n\"1e+30\"). The previous guard appended \".0\" whenever the formatted\nstring lacked a \".\" so that the literal would parse as a double\nrather than an int — but scientific notation already produces a\nvalid double literal, so appending \".0\" produced invalid output\nlike \"1e-05.0\" that the parser rejects.\n\nTreat the exponent marker \u0027e\u0027/\u0027E\u0027 as also indicating a valid double\nliteral, only appending \".0\" when neither \".\" nor \"e\"/\"E\" is\npresent.\n\nAdds regression test cases covering small/large magnitudes,\nnegative exponents, and uppercase \u0027E\u0027.\n\nFixes #1325",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ffd5b18e471f8f487aced1835471dd62738bd855",
      "old_mode": 33188,
      "old_path": "parser/unparser.go",
      "new_id": "d503a450e9df3d3f0056f895b26caa420ba2274b",
      "new_mode": 33188,
      "new_path": "parser/unparser.go"
    },
    {
      "type": "modify",
      "old_id": "11e8848be7ca7db41f1031477c786888b6115bb8",
      "old_mode": 33188,
      "old_path": "parser/unparser_test.go",
      "new_id": "7862e5ca00bb8732c2a767af45ec0d70d3fc2d22",
      "new_mode": 33188,
      "new_path": "parser/unparser_test.go"
    }
  ]
}