Johnathan Corgan dc3e7945ce Create the GitHub Release object automatically on a tag push ...

Nothing in the repository published the Release object. All five
packaging workflows run a "Wait for tag release" step that polls
`gh release view` twenty times at fifteen-second intervals and then
fails the job, so a tag push failed every packaging leg unless someone
ran `gh release create` by hand inside that five-minute budget.

The previous creator lived in package-openwrt.yml and generated the
release body from the commit list, which raced the hand-created object
and could strand the written release notes. It was removed for v0.4.2
and nothing replaced it. This adds a dedicated workflow instead, so
there is one creator, it runs as early as a tag push allows, and it
publishes `docs/releases/release-notes-<tag>.md` rather than a
generated commit list.

It is idempotent in both directions: an existing Release is left
untouched, and a Release created concurrently between the check and the
create is treated as success. A pre-release tag is marked as such and
gets the RC placeholder body, since the written notes are finalized
only for the stable tag.

(cherry picked from commit 3429fd6064a8b8ea1f87023cfccabd499696a37f)

2026-08-25 20:46:53 +01:00

..

scripts

Pin every GitHub Action to a commit SHA, and verify the nak download

2026-08-11 15:44:07 +00:00

workflows

Create the GitHub Release object automatically on a tag push

2026-08-25 20:46:53 +01:00