| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Hello 👋
You are right, this is not working due to containerization. This should be working fine if PR #692 is merged.
A possible workaround is to install poetry in the build-command ('pip install poetry; poetry install; poetry build') but it is ugly.
Hello everyone 👋🏽,
I'm facing a similar issue. More specifically, poetry fails to detect the python version passed to python-semantic-release:
The currently activated Python version 3.10.13 is not supported by the project (^3.11). Trying to find and use a compatible version. Poetry was unable to find a compatible version. If you have one, you can explicitly use it via the "env use" command. error: Encountered a bad command exit code! error: error: Command: 'pip install poetry && poetry build'
even though setup python installs the appropriate version of python:
2023-11-25T08:18:28.1280144Z Run relekang/python-semantic-release@v7.34.6 2023-11-25T08:18:28.1280994Z with: 2023-11-25T08:18:28.1282057Z github_token: *** 2023-11-25T08:18:28.1282575Z directory: . 2023-11-25T08:18:28.1283193Z env: 2023-11-25T08:18:28.1284066Z pythonLocation: /home/github/actions-runner/_work/_tool/Python/3.11.6/x64 2023-11-25T08:18:28.1285513Z PKG_CONFIG_PATH: /home/github/actions-runner/_work/_tool/Python/3.11.6/x64/lib/pkgconfig 2023-11-25T08:18:28.1286955Z Python_ROOT_DIR: /home/github/actions-runner/_work/_tool/Python/3.11.6/x64 2023-11-25T08:18:28.1288182Z Python2_ROOT_DIR: /home/github/actions-runner/_work/_tool/Python/3.11.6/x64 2023-11-25T08:18:28.1289495Z Python3_ROOT_DIR: /home/github/actions-runner/_work/_tool/Python/3.11.6/x64 2023-11-25T08:18:28.1290870Z LD_LIBRARY_PATH: /home/github/actions-runner/_work/_tool/Python/3.11.6/x64/lib
Edit: I have already tried instralling poetry using python -m pip install poetry instead of simply running pip install poetry
Could you please assist me ? Thanks!
Hello @billsioros 👋
I think your configuration don't work because the Python interpreter used in the action is python3.10, the default in debian based environment. I think the simplest fix is to allow python3.10 in your pyproject.toml.
Else you may use the specific version 8.3.0 of python-semantic-release that don't work with a docker action but with a composite action. You should still need to install python3.11 in the job step environment.
I hope this help !
Hello @zckv 👋🏽
Thank you for the prompt response! I resolved the issues by editing pyproject.toml for the time being and I'll consider migrating to v8 in the near future.
Thanks!
Hello @Yelinz 👋
This issue is still not fixed in the master branch. However, the specific tag v8.3.0 use the change in PR #692. Personally I use
- uses: python-semantic-release/python-semantic-release@v8.3.0
to have access to the environment.
I am too lazy (for now) to make a script compatible for every gitlab-runner available and complete #741. To use the PSR master branch, the hack should still work, I think.
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Still in backlog
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Still in backlog
Link #685
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Still in backlog
It has been 90 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
| Back | FazBrowse Home | New Git URL |
The problem
I am trying to use the semantic release GitHub Action. My build step is poetry build, and I am using snok/install-poetry@v1 (via packetcoders/action-setup-cache-python-poetry@main) to install Poetry. This fails with
Presumably because semantic-release is running inside a Docker container without access to the previously installed Poetry.
As a side note, my builds are incredibly slow because the two semantic-release actions must be built from dockerfiles each time. Those two build steps take almost a minute each (compared to the cached install of Python and Poetry which takes only 10 seconds total).
Expected behavior
My project is built correctly.
Environment
Ubuntu github runner with Python 3.11 and Poetry 1.6.1, but those are probably not relevant due to containerization.
The workflow looks like this:
Configuration