Skip to content

chore: automate pypi/testpypi release by tag pattern#7

Merged
aiagate merged 1 commit into
mainfrom
feature/separate-release-by-tags
Apr 13, 2026
Merged

chore: automate pypi/testpypi release by tag pattern#7
aiagate merged 1 commit into
mainfrom
feature/separate-release-by-tags

Conversation

@aiagate

@aiagate aiagate commented Apr 13, 2026

Copy link
Copy Markdown
Owner

Description

Following the implementation of dynamic versioning, this PR automates the selection of the release target (PyPI or TestPyPI) based on the Git tag pattern.

Key Changes

  • `publish-prod.yml`: Updated to trigger only on stable version tags (e.g., `v0.1.0`). Pattern: `v[0-9].[0-9].[0-9]*`.
  • `publish-test.yml`: Updated to trigger on pre-release tags (e.g., `v0.1.0rc1`, `v0.1.0a1`, `v0.1.0b1`).
  • Project URL: Fixed the TestPyPI project URL to point to `flow-res` instead of `apopy`.

Tag Naming Convention

  • TestPyPI: Use tags like `v0.1.0rc1`, `v0.1.0b1`, or `v0.1.0a1`.
  • PyPI (Production): Use tags like `v0.1.0`.

Both workflows still support manual execution via `workflow_dispatch`.

@aiagate aiagate merged commit 67d38b7 into main Apr 13, 2026
1 check passed
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