Closed gtrevisan closed 1 month ago
thanks for the suggestion!
here I'm heavily relying on poetry doing all the work, so I think we won't have any problems in replicating what poetry publish --build
might do, but it's a good point (and references to have!) in case our publishing workflow gets more complicated in the future. :grin:
revamp the Install workflow to become a Build workflow. current logic is running for:
main
anddev
,main
,The action should publish to PyPI only when triggered by a release. still, I thought it remains useful to test:
even for commits, so that we double check that no change in the code made the package impossible to build, either by creating an impossible-to-be-solved dependency checkmate (eg someone modifying project deps by hand), or by minor bugs (eg someone renaming the README.md and poetry failing to find it).
it could be simplified in case this build/build workflow wasn't adding anything to the other CI/CD tests. any suggestion is appreciated!