From 8969df945962ff0a378ce3a777c005536c32591c Mon Sep 17 00:00:00 2001
From: Yun Wang <yun.wang@getstream.io>
Date: Tue, 15 Sep 2026 16:40:08 +0200
Subject: [PATCH] fix(ci): re-run the Release PR half after a tag lands

A push merged while a release run is in flight is gated out of release-pr by the pending release, and nothing re-runs that half once the tag exists, so those commits sat unreleased until the next unrelated push.
---
 .github/workflows/release.yml | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index b019e32..7f043c4 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -141,6 +141,28 @@ jobs:
           target-branch: ${{ github.ref_name }}
           skip-github-pull-request: true
 
+  # A push that lands while the release above is running is gated out of `release-pr`,
+  # and nothing re-runs that half once the tag exists, so those commits would sit
+  # unreleased until the next unrelated push. Run it again now that the walk has a
+  # release commit to stop at.
+  release-pr-followup:
+    name: Release PR (after tagging)
+    needs: release
+    if: needs.release.outputs.release_created == 'true'
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    permissions:
+      contents: write
+      issues: write
+      pull-requests: write
+    steps:
+      - uses: googleapis/release-please-action@v4
+        with:
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json
+          target-branch: ${{ github.ref_name }}
+          skip-github-release: true
+
   # Packagist reads the tag itself; this only tells it to look now instead of on its own
   # schedule. Idempotent, so the workflow_dispatch input re-announces an existing tag.
   packagist: