Skip to content

Release 1.0.3: Use app token in release workflow - #51

Merged
AevumDecessus merged 1 commit into
fragforce:devfrom
AevumDecessus:fix-release-workflow-token
Jul 1, 2026
Merged

AevumDecessus merged 1 commit into
fragforce:devfrom
AevumDecessus:fix-release-workflow-token

Conversation

@AevumDecessus

Copy link
Copy Markdown
Contributor

Summary

Fixes prod image workflow not triggering on release events by using fragforce-automation app token instead of GITHUB_TOKEN.

Why

Events triggered by GITHUB_TOKEN do not create new workflow runs to prevent recursive workflows. This is why the prod-image workflow never triggered when releases were created - the release event was created by GITHUB_TOKEN.

Changes

  • Release workflow now generates a token from the fragforce-automation app
  • Uses app token for gh release create command
  • Release events created with app token will now trigger other workflows

Test plan

  • Merge to dev and verify CI passes
  • Create PR to main
  • Merge to main and verify v1.0.3 release creates automatically
  • Verify prod image workflow triggers via release: published event (not manual tag push)

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.
@sonarqubecloud

sonarqubecloud Bot commented Jul 1, 2026

Copy link
Copy Markdown

@AevumDecessus
AevumDecessus merged commit ce5f5ea into fragforce:dev Jul 1, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant