You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently CodeChecker pypi versions are behind on released versions, because of a disabled workflow step. See:
# FIXME: This was disabled because it was not working. We have to make sure
# that the token is appropriate. This automatic publishing is also dangerous,
# because there is no way to recover a broken release if PyPI is tainted
# (the filename will be forever locked and reserved even if we nuke a release)
Describe the solution you would like
Enable Pypi trusted publishing to re-enable the Github Workflow for easier publishing.
This can be combined with Github Environments, so a manual action (clicking a button/CI testing/...) is still required before the actual publishing is done.
For an example, see the release workflow for west from the Zephyr project.
Describe alternatives you have considered
Leave it up to the maintainers to do manual publishing, but this is error prone and requires additional effort.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Sure, but that isn't what this issue is about, but rather updating workflows to automate things.
I think it would help the project to make it easier to publish to pypi from Github actions.
Is your feature request related to a problem? Please describe.
Currently CodeChecker pypi versions are behind on released versions, because of a disabled workflow step. See:
codechecker/.github/workflows/pypi.yml
Lines 110 to 113 in 22c5e34
Describe the solution you would like
Enable Pypi trusted publishing to re-enable the Github Workflow for easier publishing.
This can be combined with Github Environments, so a manual action (clicking a button/CI testing/...) is still required before the actual publishing is done.
For an example, see the release workflow for west from the Zephyr project.
Describe alternatives you have considered
Leave it up to the maintainers to do manual publishing, but this is error prone and requires additional effort.
Additional context
N/A
The text was updated successfully, but these errors were encountered: