)]}'
{
  "commit": "e0a54fdc4bf890e11573ddd8c531dc2cdc6eac47",
  "tree": "c7b9f5b8ca32ce19ff05c4985b253b52a3adfe2d",
  "parents": [
    "f44d03d253a1503e51b059ca880867c51d878242"
  ],
  "author": {
    "name": "Daniel Tang",
    "email": "tangrs@google.com",
    "time": "Fri Aug 14 13:30:58 2026 +1000"
  },
  "committer": {
    "name": "Daniel McCarney",
    "email": "daniel@binaryparadox.net",
    "time": "Mon Aug 17 08:21:42 2026 -0700"
  },
  "message": "acme: use crypto.SignMessage instead of calling (crypto.Signer).Sign\n\ncrypto.SignMessage allows using crypto.Signers that only usefully\nimplement SignMessage to be used for the ACME account key.\n\nThis would be useful for opening up integrations with opinionated\nremote signing APIs that don\u0027t support pre-hashing.\n\nFixes golang/go#80877\n\nChange-Id: I86bb76cf5865d3d2b8606a6dbd813cbb26447c86\nReviewed-on: https://go-review.googlesource.com/c/crypto/+/815340\nReviewed-by: Daniel McCarney \u003cdaniel@binaryparadox.net\u003e\nReviewed-by: Filippo Valsorda \u003cfilippo@golang.org\u003e\nReviewed-by: Sean Liao \u003csean@liao.dev\u003e\nLUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com \u003cgolang-scoped@luci-project-accounts.iam.gserviceaccount.com\u003e\nReviewed-by: Carlos Amedee \u003ccarlos@golang.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6850275665f87cda1ce6306bc2c0d466d220eb85",
      "old_mode": 33188,
      "old_path": "acme/jws.go",
      "new_id": "2df17dddb6fa77cc4087a3a9a68c62bdeb79883b",
      "new_mode": 33188,
      "new_path": "acme/jws.go"
    }
  ]
}