Repository navigation
Releasing a python >=3.11 package #801
Description
It looks like python 3.10 is used to do the releasing, but I have a package that is python 3.11+ only home-assistant-libs/home-assistant-bluetooth#30
This means the release workflow fail since The currently activated Python version 3.10.13 is not supported by the project (>=3.11,<3.13). Trying to find and use a compatible version.
sample run: https://github.com/home-assistant-libs/home-assistant-bluetooth/actions/runs/7482007644/job/20364775062
Is there an approved/good way to use a newer python in the build process?
Activity
[-]Releasing a python 3.11+ package[/-][+]Releasing a python >=3.11 package[/+]codejedi365 commentedon Jan 11, 2024
After reviewing your logs, this does not look like a semantic-release problem.
When semantic-release runs your build command, you have a number of errors that happen. First, pip throws errors about being unable to write to the cache, then it fails to resolve some dependency conflicts. Poetry is the one throwing the error about the python version I believe.
Just checked your CI configuration and you didn't set up your python environment in your release job. It can't find the right python version because of this, I believe.
Or you may have a similar issue to #723
bdraco commentedon Jan 11, 2024
It looks like its definitely running setup python before the failing step.
I guess its using the wrong python somehow
bdraco commentedon Jan 11, 2024
I think the setup python is running outside the container, and its 3.10.x in the container
bdraco commentedon Jan 11, 2024
I got it to work by forking it and adjusting the python version in the docker file
Bluetooth-Devices@e7976f0
codejedi365 commentedon Jan 12, 2024
@bdraco, my mistake, I think I was looking at the wrong job / pipeline earlier. Yes, good job finding a solution. I didn't write the GitHub Action and I didn't realize it was its own container which does hardcode the python version.
I'm not sure what the best course of action is here for compatibility (other than not use docker to distribute the action)... will have to think on it. Thank you for bringing it to our attention.
bdraco commentedon Jan 12, 2024
Thanks for looking.
cheers
build(deps): bump GitHub Action container to use `python3.12`
build(deps): bump GitHub Action container to use `python3.12`
build(deps): bump GitHub Action container to use `python3.12`
build(deps): bump GitHub Action container to use `python3.12`
refactor: optimize & improve maintainability of GitHub Action definit…
bdraco commentedon May 6, 2024
Thanks!
codejedi365 commentedon May 6, 2024
🎉 This issue has been resolved in version 9.7.0 🎉
The release is available on: