Fix release notification workflow startup#5394
Merged
Merged
Conversation
clockwork-labs-bot
requested review from
bfops,
cloutiertyler and
jdetter
as code owners
bfops
reviewed
Jun 18, 2026
Signed-off-by: Zeke Foppa <196249+bfops@users.noreply.github.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
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.
Description of Changes
Fixes the
Release Notificationsworkflow startup failure seen in https://github.com/clockworklabs/SpacetimeDB/actions/runs/27775721225/workflow.The internal announcement job referenced
needs: on-release, but noon-releasejob exists in.github/workflows/tag-release.yml, so the workflow failed before scheduling any jobs. This removes the dangling dependency and gates the internal Discord announcement to realreleaseevents so manualworkflow_dispatchdry runs do not try to send an internal release announcement using missing release-event fields.API and ABI breaking changes
None. This only changes GitHub Actions configuration.
Expected complexity level and risk
1 - Low complexity. The change is limited to one workflow job dependency/condition.
Testing
.github/workflows/tag-release.ymlas YAML.needs:targets in.github/workflows/tag-release.ymlrefer to existing jobs.git diff --check.