From 48f3822a993be6b65295cfffa7ab7a1f56695bb0 Mon Sep 17 00:00:00 2001 From: Yun Wang Date: Tue, 15 Sep 2026 17:23:15 +0200 Subject: [PATCH] ci: drop the redundant post-tag Release PR job Added in 30419f4 for a gap that does not exist. The workflow concurrency group already covers it: a push during a release run goes pending rather than running, and starts only once the tag exists and the label has flipped, so its own detect reports no pending release and release-pr runs. --- .github/workflows/release.yml | 22 ---------------------- 1 file changed, 22 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 255a03a..3360099 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -140,28 +140,6 @@ 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 - # Chained rather than triggered on the release event, because a GitHub Release created # with GITHUB_TOKEN starts no new workflow run. Also reachable on its own through # workflow_dispatch with publish_tag, which is the recovery path once GitHub has