fix: include phylum-ci.exe
in release artifacts
#477
Merged
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.
This change corrects a bug in the release workflow where the
phylum-ci.exe
artifact is not published to the newly created GitHub release. Thepython-semantic-release
tool has the following config, inpyproject.toml
, for publishing artifacts by pattern:The issue was that the
actions/upload-artifact
step usedphylum-ci.exe
as the artifact name, which resulted in the following directory structure for the correspondingactions/download-artifact
step:./phylum-ci.exe/phylum-ci.exe
This clearly won't match the glob pattern of
build/phylum-ci.exe
. So, this change is a simple one: change the upload artifact name tobuild
so that the downloaded artifact will exist at./build/phylum-ci.exe
.