Release - Reject direct public release invocations - #5850
Merged
Conversation
clockwork-labs-bot
requested review from
bfops,
cloutiertyler,
jdetter and
rekhoff
as code owners
August 31, 2026 15:42
rekhoff
approved these changes
Aug 31, 2026
rekhoff
left a comment
Contributor
There was a problem hiding this comment.
LGTM, this would save us from accidental invocation
This was referenced Aug 31, 2026
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
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
Adds an initial release workflow validation job that rejects manual public release invocations unless the workflow actor is
spacetimedb-devops.The public release workflow is intended to be dispatched by the internal automated release workflow. Direct human invocations now fail before any release job can build or publish artifacts, with an explicit error telling the operator to use the internal release workflow.
API and ABI breaking changes
None.
Expected complexity level and risk
1
Testing