tree a25b6cb22654fda2c031b5839cd4fcbd44562077
parent 81024dd4d92c2f926dbae0405802871d490765d1
author Marc Kupietz <kupietz@ids-mannheim.de> 1788238637 +0200
committer Marc Kupietz <kupietz@ids-mannheim.de> 1788238662 +0200

CI: create GitHub releases from NEWS.md on version tags

Pushing a v<version> tag now creates the corresponding GitHub release
automatically, with the matching section of NEWS.md as release notes,
following the naming used so far ("RKorAPClient v1.2.1 (CRAN-Release)").

The notes are cut out between the level 1 NEWS.md heading that mentions
the tagged version and the next level 1 heading, so that headings like
"# RKorAPClient 0.7.5 (CRAN release)" are matched as well, while level 2
headings inside a section are kept. Versions are matched as whole
tokens, so that v1.2.1 does not pick up a "1.2.1.9000" dev section.

The job fails if NEWS.md has no section for the tagged version, rather
than publishing an empty release, and warns if the tag disagrees with
the version in DESCRIPTION. Tags that are not x.y.z are marked as
pre-releases. Re-running on an existing release updates it instead of
failing, and workflow_dispatch allows generating the notes for a tag
that was pushed before this workflow existed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Change-Id: I2bee9d30e3894c92d5f35f077895388b19c5e5cc