)]}'
{
  "commit": "ae4079aee782740315e3c8d7cb6f19dbe1f73df8",
  "tree": "a25b6cb22654fda2c031b5839cd4fcbd44562077",
  "parents": [
    "81024dd4d92c2f926dbae0405802871d490765d1"
  ],
  "author": {
    "name": "Marc Kupietz",
    "email": "kupietz@ids-mannheim.de",
    "time": "Tue Sep 01 06:57:17 2026 +0200"
  },
  "committer": {
    "name": "Marc Kupietz",
    "email": "kupietz@ids-mannheim.de",
    "time": "Tue Sep 01 06:57:42 2026 +0200"
  },
  "message": "CI: create GitHub releases from NEWS.md on version tags\n\nPushing a v\u003cversion\u003e tag now creates the corresponding GitHub release\nautomatically, with the matching section of NEWS.md as release notes,\nfollowing the naming used so far (\"RKorAPClient v1.2.1 (CRAN-Release)\").\n\nThe notes are cut out between the level 1 NEWS.md heading that mentions\nthe tagged version and the next level 1 heading, so that headings like\n\"# RKorAPClient 0.7.5 (CRAN release)\" are matched as well, while level 2\nheadings inside a section are kept. Versions are matched as whole\ntokens, so that v1.2.1 does not pick up a \"1.2.1.9000\" dev section.\n\nThe job fails if NEWS.md has no section for the tagged version, rather\nthan publishing an empty release, and warns if the tag disagrees with\nthe version in DESCRIPTION. Tags that are not x.y.z are marked as\npre-releases. Re-running on an existing release updates it instead of\nfailing, and workflow_dispatch allows generating the notes for a tag\nthat was pushed before this workflow existed.\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\nChange-Id: I2bee9d30e3894c92d5f35f077895388b19c5e5cc\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "7b68c18f3d3118b68a7b6c6a289bdc773a3dc902",
      "new_mode": 33188,
      "new_path": ".github/workflows/release.yaml"
    }
  ]
}