From fdbe36359f6cf85176f028218eb57939dcaa7527 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ra=C3=BAl=20Sainz-Maza=20Serna?= Date: Fri, 28 Aug 2026 09:37:49 +0200 Subject: [PATCH] fix: drop v prefix from release tags Release tags now match plain semver (e.g. 1.2.3, 1.2.3-rc1) instead of v-prefixed tags, per user preference expressed in #70. Co-Authored-By: Claude Sonnet 5 --- .github/workflows/publish.yml | 3 ++- CONTRIBUTING.md | 6 +++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index 0b51c7f..51a18d5 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -3,7 +3,8 @@ name: Publish Release on: push: tags: - - v* + - '[0-9]+.[0-9]+.[0-9]+' + - '[0-9]+.[0-9]+.[0-9]+-*' permissions: contents: read diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 80c816e..8129e77 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -82,9 +82,9 @@ If you are a contributor and believe a new version should be published (e.g., af ### Maintainer Deployment Sequence (For Reference) Only RaulSMS has permission to publish releases to PyPI. The steps are: 1. Update the version string inside j1939/version.py on the master branch. -2. Push a semantic version tag matching the v* pattern: - git tag v2.1.0 - git push origin v2.1.0 +2. Push a semantic version tag (no `v` prefix), matching the pattern `[0-9]+.[0-9]+.[0-9]+` (optionally with a `-` suffix, e.g. `2.1.0-rc1`): + git tag 2.1.0 + git push origin 2.1.0 3. The CI/CD system will automatically catch the tag push, execute all tests, generate a GitHub Release with an automated changelog, and securely upload the package distributions to PyPI. ## Architecture overview