In the pipeline defined in release.yml currently uses a hard coded python version for building the packages.
|
- name: Set up Python 3.10 |
|
uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v7 |
|
with: |
|
python-version: "3.10" |
Additionally, the definition of the two build jobs is explicit here and never tested before release time. The pr.yml pipeline tests the builds but it is not ensured that these jobs (sdk-package and compliance-tool-package) actually test the CI implementation that is used in release.yml. We should consider using a composite action for building packages too.
In the pipeline defined in
release.ymlcurrently uses a hard coded python version for building the packages.basyx-python-sdk/.github/workflows/release.yml
Lines 22 to 25 in 22a46f5
Additionally, the definition of the two build jobs is explicit here and never tested before release time. The
pr.ymlpipeline tests the builds but it is not ensured that these jobs (sdk-packageandcompliance-tool-package) actually test the CI implementation that is used inrelease.yml. We should consider using a composite action for building packages too.