chore: use centralized build-python-version for PublishToPyPI#1104
Merged
epmog merged 1 commit intoaws-deadline:mainlinefrom Apr 15, 2026
Merged
Conversation
Use the build-python-version output from the shared TagRelease workflow instead of a hardcoded Python version. This ensures all repos stay in sync when build tool requirements change (e.g. hatchling 1.29.0 requiring Python >=3.10). Signed-off-by: Stephen Crowe <6042774+crowecawcaw@users.noreply.github.com>
|
github-actions
Bot
added
the
waiting-on-maintainers
epmog
approved these changes
Apr 14, 2026
epmog
changed the title
mwiebe
approved these changes
Apr 15, 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
3 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
Use the
build-python-versionoutput from the sharedTagReleaseworkflow instead of a hardcoded Python version in thePublishToPyPIjob.Motivation
hatchling1.29.0 dropped Python 3.9 support (requires>=3.10), breakingPublishToPyPIin repos still usingpython-version: '3.9'. By referencing a centralized output from aws-deadline/.github#74, all repos stay in sync when build tool requirements change.Depends on
build-python-versionoutput toreusable_tag_release.yml)