fix: explicit dev suffix - #27
Merged
Merged
Conversation
Inside a called workflow github.event_name is the CALLER's event. So a manual run of upstream-release-watch reported a release while publishing Tero-Datadog-Extension-<N>-dev, because the caller's event was workflow_dispatch. Only the scheduled path published prod names. Drive the suffix from an explicit `dev` input instead: true by default for workflow_dispatch so a manual run cannot overwrite a real release, false for workflow_call so watch-driven releases are real however the watch was triggered. Tag pushes leave the input empty and are never -dev. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
smithclay
approved these changes
Aug 20, 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
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.
Please include Jira ticket in title.
Overview
Testing