From c7f51c3a9a94dc33825dd6bb2f5e87d28574cfc2 Mon Sep 17 00:00:00 2001 From: Alessandro Rinaldi Date: Tue, 21 Jul 2026 23:50:35 +0200 Subject: [PATCH] ci: mark PEP 440 pre-release tags as GitHub pre-releases Tags like v1.2.0b1 / v1.2.0rc1 now produce a GitHub pre-release (PyPI already treats the version as a pre-release), so beta cuts are labelled consistently for the upcoming port-8888 test rounds. Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/publish.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index 503c3a4..78c2b12 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -97,3 +97,7 @@ jobs: with: body_path: RELEASE_BODY.md generate_release_notes: true + # PEP 440 pre-release tags (e.g. v1.2.0b1, v1.2.0rc1) → GitHub pre-release. + # PyPI already treats the version itself as a pre-release; this keeps the + # GitHub release labelled consistently. + prerelease: ${{ contains(github.ref_name, 'b') || contains(github.ref_name, 'rc') }}