fix: add workflow_dispatch trigger to release-drafter#24
Merged
Conversation
The push-on-develop trigger misses commits when the merge lands via an action that uses GITHUB_TOKEN (notably the automerge.yaml flow), because GitHub doesn't fire downstream workflows from a token-driven push. Adding workflow_dispatch lets the operator refresh the draft manually with `gh workflow run release-drafter.yml --ref develop` whenever the push-based run gets skipped. The push trigger stays the default path; workflow_dispatch is the documented manual fallback. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a
workflow_dispatchtrigger to.github/workflows/release-drafter.ymlso the draft release can be refreshed manually when the standard
pushtriggergets skipped. Today, every merge that lands via
automerge.yamluses thedefault
GITHUB_TOKEN, and GitHub doesn't fire downstream workflows from atoken-driven push — so
release-drafterhasn't run since 2026-04-22 eventhough PRs #21, #22, and #23 have since merged to
develop.Changes
workflow_dispatch:to theon:block ofrelease-drafter.yml.(token-driven pushes don't trigger downstream workflows).
Linked issues
None
Testing
pre-commit run --files .github/workflows/release-drafter.yml: passed.gh workflow run release-drafter.yml --ref developto refresh the open draft
v0.1.4so it picks up PRs docs: add per-module pages, README table, and small src cleanup #21–docs: add AUDIENCES.md per audience-identification spec #23, then resumerelease-notes-curate.Risk / rollout notes
Low risk — adds a manual trigger to an existing workflow. The
pushtriggerstays the default path;
workflow_dispatchis the documented manual fallback.The root cause (
GITHUB_TOKENnot firing downstream workflows from theautomerge action) is a separate upstream fix in
nolte/gh-plumbingand isout of scope for this PR.