Release 1.0.3 - #52
Merged
Merged
Conversation
Events triggered by GITHUB_TOKEN do not create new workflow runs to prevent recursive workflows. This prevented the prod image workflow from triggering when releases were created. Using the fragforce-automation app token instead allows the release event to properly trigger the prod-image workflow.
Release 1.0.3: Use app token in release workflow
|
parkervcp
approved these changes
Jul 1, 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.
Summary
Release 1.0.3 with fix for release workflow to properly trigger prod image builds.
Changes
Why
Events triggered by GITHUB_TOKEN do not create new workflow runs to prevent recursive workflows. This prevented the prod-image workflow from triggering when releases were created.
Test plan
release: publishedevent (NOT manual tag push)