ci: allow publishing pre-release versions to PyPI#11
Merged
AdityaGolatkar merged 1 commit intostrands-labs:mainfrom Apr 30, 2026
Merged
Conversation
Relax the version-validation regex in the PyPI publish workflow to accept PEP 440 pre-release suffixes, so tags like v0.2.0a2 can be released. Also echo the version in the validation output to make failures easier to diagnose.
AdityaGolatkar
approved these changes
Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pypi-publish-on-release.ymltoaccept PEP 440 pre-release suffixes (
aN,bN,rcN), so tags such asv0.2.0a2are publishable.on failure.
Pre-releases are safe to publish:
pip install strands-ai-functionskeepsresolving to the latest stable unless the user passes
--preor pins an exactpre-release version.