We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The new release v0.5.0 is not on PyPI.
Debugging the problem I can see that in the first attempt the uploaded version results in v0.0.0 which is of course wrong https://github.com/cta-observatory/protopipe/actions/runs/2168145005/attempts/1
I think the problem is that setuptools_scm is not supported by the current deploy workflow, which is in fact different from that of ctapipe (the last but one release was so old that this was not a problem...) https://github.com/cta-observatory/ctapipe/blob/0612a333c87cbb7c39b3a82c4663082e77eceb72/.github/workflows/deploy.yml#L22-L26
The text was updated successfully, but these errors were encountered:
opened #192 to attempt to fix this
Sorry, something went wrong.
the problem is that the workflow gets triggered only by a tag pushed as "v*" (a release with this name triggers it)
that PR alone won't cut it...
No branches or pull requests
The new release v0.5.0 is not on PyPI.
Debugging the problem I can see that in the first attempt the uploaded version results in v0.0.0 which is of course wrong
https://github.com/cta-observatory/protopipe/actions/runs/2168145005/attempts/1
I think the problem is that setuptools_scm is not supported by the current deploy workflow, which is in fact different from that of ctapipe (the last but one release was so old that this was not a problem...)
https://github.com/cta-observatory/ctapipe/blob/0612a333c87cbb7c39b3a82c4663082e77eceb72/.github/workflows/deploy.yml#L22-L26
The text was updated successfully, but these errors were encountered: