Skip to content

ci: drop the redundant post-tag Release PR job #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mogita merged 1 commit into from
Sep 15, 2026
Merged

ci: drop the redundant post-tag Release PR job #97

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 0 additions & 22 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading