chore(release): fix download path for PublishToPyPI step#294
Merged
jericht merged 1 commit intoJun 25, 2026
Merged
Conversation
Signed-off-by: Jericho Tolentino <68654047+jericht@users.noreply.github.com>
seant-aws
approved these changes
Jun 25, 2026
leongdl
approved these changes
Jun 25, 2026
godobyte
approved these changes
Jun 25, 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
4 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.
What was the problem/requirement? (What/Why)
I fixed the GitHub release, but now the PublishToPyPI step is failing: https://github.com/OpenJobDescription/openjd-model-for-python/actions/runs/28205044422/job/83555345059
Root cause is that the artifacts are downloaded into
dist/distfolder, and the double dist folder is causing the PyPI publish to not see the artifactsWhat was the solution? (How)
Remove the redundant dist folder
What is the impact of this change?
PublishToPyPI works
How was this change tested?
N/A - this download-artifacts call matches the one in
reusable_release.yml, which we confirmed works in the above workflow: (see source code)Was this change documented?
No
Is this a breaking change?
No
Does this change impact security?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.