Skip to content

Publish to PyPI on four-part version tags - #156

Merged
dstebila merged 1 commit into
mainfrom
publish-pypi-four-part-tags
Sep 22, 2026
Merged

dstebila merged 1 commit into
mainfrom
publish-pypi-four-part-tags

Conversation

@dstebila

Copy link
Copy Markdown
Member

The PyPI publish workflow triggers only on three-part version tags:

tags:
  - "[0-9]+.[0-9]+.[0-9]+"

This means a maintenance release tagged 0.16.0.1 would not trigger a publish, and the release would have to be uploaded by hand. Four-part versions are useful here because they leave the next three-part version free to match the corresponding liboqs release.

This adds a second tag pattern so both forms trigger the workflow:

tags:
  - "[0-9]+.[0-9]+.[0-9]+"
  - "[0-9]+.[0-9]+.[0-9]+.[0-9]+"

No other behaviour changes — the job itself is untouched, and three-part tags continue to work exactly as before.

🤖 Generated with Claude Code

Allow maintenance releases such as 0.16.0.1 to trigger the PyPI publish
workflow, which previously matched only three-part tags.

Signed-off-by: Douglas Stebila <dstebila@uwaterloo.ca>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@dstebila
dstebila merged commit 455fc21 into main Sep 22, 2026
10 checks passed
@dstebila
dstebila deleted the publish-pypi-four-part-tags branch September 22, 2026 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant