Auto-trigger the Xposed mirror from release.yml#13
Merged
Conversation
The release.yml-published release is authored by GITHUB_TOKEN, and GitHub won't start another workflow from a GITHUB_TOKEN-created release event, so the xposed-release 'release: published' trigger never fired for auto-cut releases. Dispatch xposed-release.yml explicitly at the end of release.yml instead (workflow_dispatch is an allowed exception), and grant the job actions: write so it can dispatch. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UMXydF1vt9Y1NKsncTN6gd
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.
Why
After #12, the
xposed-releasemirror was wired to run onrelease: published, but that trigger never fires for our auto-cut releases:release.ymlpublishes the release using the defaultGITHUB_TOKEN, and GitHub deliberately won't start another workflow from aGITHUB_TOKEN-authoredreleaseevent (anti-recursion). Verified live — the mirror had 0 runs afterv1.0.8was cut.What
release.ymlnow explicitly dispatchesxposed-release.ymlas its final step (gh workflow run … -f tag=<tag>).workflow_dispatchis an allowed exception to theGITHUB_TOKENrule, so this reliably kicks the mirror after each release.actions: writeso it can dispatch.The
release: publishedand manualworkflow_dispatchpaths from #12 still work; this just makes the automatic path fire.Verification
Manually dispatched the mirror for the existing
v1.0.8(token now configured). Run succeeded, and the entry repo now has a compliant release:Xposed-Modules-Repo/com.xiddoc.playintegrityalert→ tag22-1.0.8(VersionCode-VersionName) with assetPlayIntegrityAlert-v1.0.8.apk, README/SUMMARY/SOURCE_URL synced.🤖 Generated with Claude Code
Generated by Claude Code