Python CLI Publication: Github workflow to build artifacts

[HonahX]

Is your feature request related to a problem? Please describe.

Since python CLI contains open api generated code and we do not want user to generate it again when installing the package, we want to build wheels for multiple Operating Systems.

We need to build 2 kinds of artifacts

1. artifacts uploaded to svn and pypi upon release verification and final publication
2. artifacts uploaded to pypi as pre-release (or nightly build)

The main difference between 1 and 2 are the package version: e.g. (1.2.0 and 1.2.0rc1)

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

[binarycat0]

🔆 Just to highlight that in this dev@ thread was discussed legal and versioning aspects. AFAIK, Before setting a version it's better to be sure that PPMCs are agree or even better to have a validated VOTE dev@ thread.

[HonahX]

Hi @binarycat0 Thanks for highlighting here. The final version for publication was not set by the github workflow but in the project metadata. We should reach a consensus on the version before voting on artifact. I think this could be a separate issue/task to track. The workflow only focusing on attaching an rc postfix to the version for pypi artifact in order to publish a pre-release version. WDYT?