Name and Version
all
What steps will reproduce the bug?
run python_package_release workflow
What is the expected behavior?
In Publish to pypi step of release job, the package is built, then published
What do you see instead?
In Publish to pypi step of release job, the package is built, then built again, then published
Additional information
Suggestion:
instead of
keep only make publish and add a Makefile example, where the targets are bound, e.g.
build:
$(POETRY) build
publish: build
$(POETRY) publish -u __token__ -p $(PYPI_TOKEN) --skip-existing
Name and Version
all
What steps will reproduce the bug?
run python_package_release workflow
What is the expected behavior?
In
Publish to pypistep ofreleasejob, the package is built, then publishedWhat do you see instead?
In
Publish to pypistep ofreleasejob, the package is built, then built again, then publishedAdditional information
Suggestion:
instead of
keep only
make publishand add a Makefile example, where the targets are bound, e.g.