chore(publish): route package releases through dispatcher#377
Merged
Charles Hudson (phobetron) merged 1 commit intoJul 15, 2026
Merged
Conversation
GitHub release events cannot be tag-filtered, so each published package release was starting all publish workflows and relying on job-level skips. Add a release dispatcher that routes known release tags to the matching workflow_dispatch target, and make the npm, Android, and Swift publish workflows dispatch-only. Resolve npm publish targets from the dispatched tag so multi-tag release commits do not bleed into unrelated package runs. [[NT-3710](https://contentful.atlassian.net/browse/NT-3710)]
Tim Beyer (TimBeyer)
approved these changes
Jul 15, 2026
Charles Hudson (phobetron)
deleted the
NT-3710_reducing-release-workflow-noise
branch
July 15, 2026 12:27
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
2 participants
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
Dispatch Package Publishworkflow forrelease.publishedevents.workflow_dispatchtargets that useinputs.tag.Why
GitHub
releasetriggers do not support tag filters. Because release PR #376 put all package tags on the same merge commit, every published release woke all package publish workflows, causing skipped Android/Swift runs for npm releases and canceled/skipped npm runs for native releases.This keeps release publishing automatic, but moves the fan-out decision into one dispatcher.
[NT-3710]