grabowski d7c3089031 Release notes come from a file in the repo, not the tag ...

Deriving the body from the tag annotation does not survive CI: the
release action does not fall back to it (v1.2.0 published empty), and
checkout leaves the tag lightweight, so %(contents) yields the commit
message instead - which is what v1.2.1 first published. Keep the notes
at docs/release-notes/v<version>.md, pass that as body_path, and fail
the run when it is missing.

2026-07-22 16:27:31 +07:00

..

workflows

Release notes come from a file in the repo, not the tag

2026-07-22 16:27:31 +07:00