From 3ed5cff18bd36eca277555ff6767304c6c29200f Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Thu, 2 Jul 2026 12:43:10 +0000
Subject: [PATCH] Trigger the Xposed mirror from release.yml

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
---
 .github/workflows/release.yml | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 8ee8554..aa46460 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -15,6 +15,8 @@ concurrency:
 
 permissions:
   contents: write
+  # actions: write lets the final step dispatch the xposed-release workflow.
+  actions: write
 
 jobs:
   release:
@@ -102,3 +104,15 @@ jobs:
           generate_release_notes: true
           fail_on_unmatched_files: true
           files: ${{ steps.apk.outputs.path }}
+
+      - name: Mirror the release into the Xposed Modules Repo
+        # The release above is authored by GITHUB_TOKEN, and GitHub deliberately
+        # won't start another workflow from a GITHUB_TOKEN-created `release` event
+        # (anti-recursion). workflow_dispatch is an explicit exception, so we kick
+        # xposed-release.yml directly here to mirror the release we just published.
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          gh workflow run xposed-release.yml \
+            --ref "${{ github.ref_name }}" \
+            -f tag="${{ steps.version.outputs.tag }}"