Switch post-release to repository_dispatch trigger

The workflow_run event only provides head_branch (PR source branch),
not the target branch. This caused git describe --tags to find wrong
tags when releasing from non-main branches like 8.0-stable.

Using repository_dispatch allows the release workflow to explicitly
pass the target_branch to post-release, ensuring correct tag detection.

Author: tvdeyen

.github/workflows/post-release.yml

@@ -1,17 +1,22 @@
 name: Post Release
 
 on:
-  workflow_run:
-    workflows: ["Publish Release"]
-    types:
-      - completed
+  workflow_dispatch:
+    inputs:
+      target_branch:
+        description: 'Target branch (e.g., main, 8.0-stable)'
+        required: true
+        default: 'main'
+        type: string
+  repository_dispatch:
+    types: [post-release]
 
 jobs:
-  bump-dev-version:
-    if: github.event.workflow_run.conclusion == 'success'
+  post-release:
     uses: AlchemyCMS/.github/.github/workflows/post-release.yml@main
     with:
       version_file_path: lib/alchemy/devise/version.rb
+      target_branch: ${{ github.event.client_payload.target_branch || inputs.target_branch }}
     secrets:
       app_id: ${{ vars.ALCHEMY_BOT_APP_ID }}
       app_private_key: ${{ secrets.ALCHEMY_BOT_APP_PRIVATE_KEY }}

.github/workflows/release.yml

@@ -13,6 +13,7 @@ jobs:
     uses: AlchemyCMS/.github/.github/workflows/release.yml@main
     with:
       version_file_path: lib/alchemy/devise/version.rb
+      target_branch: ${{ github.event.pull_request.base.ref || github.ref_name }}
     secrets:
       app_id: ${{ vars.ALCHEMY_BOT_APP_ID }}
       app_private_key: ${{ secrets.ALCHEMY_BOT_APP_PRIVATE_KEY }}