Adds workflow_dispatch with a required tag input to announce.yml and passes it to discourse-release, which already supports tag. On a release event the input is empty, so nothing changes there.
Why: the announcement for inbuxa-v2026.10.5-g17a8093 failed on the unmapped repo name. #39 fixed the pin on main, but a re-run of a release event uses the workflow at the tag (old pin), so it would fail again. After this lands, dispatching it with that tag announces the release once (the action dedupes per repo+tag).
Adds `workflow_dispatch` with a required `tag` input to announce.yml and passes it to discourse-release, which already supports `tag`. On a release event the input is empty, so nothing changes there.
Why: the announcement for inbuxa-v2026.10.5-g17a8093 failed on the unmapped repo name. #39 fixed the pin on main, but a re-run of a release event uses the workflow at the tag (old pin), so it would fail again. After this lands, dispatching it with that tag announces the release once (the action dedupes per repo+tag).
A release event runs the workflow as it was at the tag, so re-running a
failed announcement repeats the failure even after main is fixed. A manual
run takes the tag and uses main's workflow; the action already accepts it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds
workflow_dispatchwith a requiredtaginput to announce.yml and passes it to discourse-release, which already supportstag. On a release event the input is empty, so nothing changes there.Why: the announcement for inbuxa-v2026.10.5-g17a8093 failed on the unmapped repo name. #39 fixed the pin on main, but a re-run of a release event uses the workflow at the tag (old pin), so it would fail again. After this lands, dispatching it with that tag announces the release once (the action dedupes per repo+tag).