Fix Up PyPI Upload Process #3208
Merged
Conversation
This file contains 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
SorenSpicknall
changed the title
SorenSpicknall
requested review from
evansiroky and
hunterowens
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Upon merge of #3204, publication to PyPI was unsuccessful for the
calitp-data-infrapackage (it was skipped forcalitp-data-analysisbecause the current version number matched the published version number). This PR makes a change to a mistyped environment variable assignment in the publication YML forcalitp-data-analysiswhich should resolve the issue based on my understanding of Poetry's environment variable construction norms. If not, there is an additional step we can take next.Type of change
How has this been tested?
Uploads made to TestPyPI based on similar environment variable structure - since this workflow only fires to prod upon merge, if this set of changes doesn't work an additional PR will be created for the next set of changes.
Post-merge follow-ups