gecka-release.yml publishes through softprops/action-gh-release without setting name, so the release title defaults to the bare tag (v1.4.9). The message we put on the annotated tag (e.g. 🥥 v1.4.9 — Freshly cracked) only shows on the Tags page, not on the release, so right now it has to be fixed by hand with gh release edit --title after every build.
Would rather read the tag subject in the workflow and feed it to the action's name:
git for-each-ref refs/tags/$GITHUB_REF_NAME --format='%(contents:subject)'
Two things to watch: the checkout has to fetch the tag or the annotation isn't there, and name has to be set on all four publish jobs (windows/linux/macos/android) since they target the same release.
gecka-release.ymlpublishes throughsoftprops/action-gh-releasewithout settingname, so the release title defaults to the bare tag (v1.4.9). The message we put on the annotated tag (e.g.🥥 v1.4.9 — Freshly cracked) only shows on the Tags page, not on the release, so right now it has to be fixed by hand withgh release edit --titleafter every build.Would rather read the tag subject in the workflow and feed it to the action's
name:Two things to watch: the checkout has to fetch the tag or the annotation isn't there, and
namehas to be set on all four publish jobs (windows/linux/macos/android) since they target the same release.