From aea42e3bc1fdcdde584fe206cf9308151a358762 Mon Sep 17 00:00:00 2001
From: Mitja Kleider <48825+emka@users.noreply.github.com>
Date: Tue, 6 Oct 2026 14:58:13 +0200
Subject: [PATCH] ci(release): publish the release when its pull request is
 merged

Merging a release pull request is the decision to release, so nothing
should be left to remember afterwards. Opening the pull request stays
manual: a push to main must not open or update one until a release is
wanted.
---
 .github/workflows/release-please.yml | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.yml
index a99ec44..250c2db 100644
--- a/.github/workflows/release-please.yml
+++ b/.github/workflows/release-please.yml
@@ -1,8 +1,11 @@
 name: Release
 
-# Run by hand from the Actions tab: a push to main must not open or update a
-# release pull request until a release is wanted.
+# A release pull request is opened or updated only when this workflow is run by
+# hand from the Actions tab. A push to main only publishes the tag and the
+# GitHub release of a release pull request that has just been merged.
 on:
+  push:
+    branches: [main]
   workflow_dispatch:
 
 permissions:
@@ -31,5 +34,6 @@ jobs:
           # the failure would surface only after merge, against a published
           # tag.
           token: ${{ secrets.GH_CI_TOKEN }}
+          skip-github-pull-request: ${{ github.event_name == 'push' }}
           config-file: release-please-config.json
           manifest-file: .release-please-manifest.json