From 750d7141ed90182da9b1d48e70bcb96873a55898 Mon Sep 17 00:00:00 2001
From: capskip <support@capskip.com>
Date: Sun, 26 Jul 2026 04:33:06 +0800
Subject: [PATCH] Create a GitHub release when a version tag is published

Tagging published the package to PyPI but never created a release, so
the repo's Releases page stayed on the previous version. The PHP SDK's
workflow already did this; this brings Python in line.

Notes are auto-generated from merged PRs and can be edited afterwards. The
job now needs contents: write to create the release.
---
 .github/workflows/publish.yml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
index b9e2a72..be1095b 100644
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -16,6 +16,7 @@ jobs:
       name: pypi
       url: https://pypi.org/project/capskip/
     permissions:
+      contents: write # required to create the GitHub release
       id-token: write
 
     steps:
@@ -40,3 +41,12 @@ jobs:
         with:
           # Don't fail if this version's files are already on PyPI (e.g. a re-run tag).
           skip-existing: true
+
+      # Without this the tag ships to PyPI but never appears on the repo's
+      # Releases page. Notes are auto-generated from merged PRs and can be
+      # edited afterwards.
+      - name: Create GitHub release
+        uses: softprops/action-gh-release@v2
+        with:
+          name: CapSkip Python SDK ${{ github.ref_name }}
+          generate_release_notes: true