search

wilson-eft / wilson

A Python package for the running and matching of Wilson coefficients above and below the electroweak scale
https://wilson-eft.github.io
MIT License
26 stars 19 forks source link

Upload of wilson v2.3 to PyPI #98

Closed peterstangl closed 2 years ago

peterstangl commented 2 years ago

@jasonaebischerGIT @dvandyk @klieret @DavidMStraub I just released wilson v2.3 but the upload to PyPI didn't work and I realized that only you are PyPI maintainers of wilson. It would be nice if one of you could upload the latest release to PyPI.

DavidMStraub commented 2 years ago

Hi, why did the workflow fail?

peterstangl commented 2 years ago

I thought it didn't work since I'm not a maintainer on PyPI, but actually it seems that the workflow was not triggered at all by the new release and I don't know why.

DavidMStraub commented 2 years ago

Looking into it. It did run but this IF https://github.com/wilson-eft/wilson/blob/master/.github/workflows/check%2Bdeploy.yaml#L72 evaluated to false. Offending line added by @dvandyk in https://github.com/wilson-eft/wilson/commit/3660307a5db98a5ba39fad9bf04080d7c3462fcb.

DavidMStraub commented 2 years ago

Uploaded to PyPI, but the workflow should be fixed.

peterstangl commented 2 years ago

Looking into it. It did run but this IF https://github.com/wilson-eft/wilson/blob/master/.github/workflows/check%2Bdeploy.yaml#L72 evaluated to false. Offending line added by @dvandyk in 3660307.

Where do you see this? I don't see any workflow run for the release at all. The last workflow run I see is from the commit that changed the version number and there this IF in https://github.com/wilson-eft/wilson/blob/master/.github/workflows/check%2Bdeploy.yaml#L72 evaluates to false since it was a commit and not a release that has triggered the event. Were you looking at that one?

dvandyk commented 2 years ago

Looking into it. It did run but this IF https://github.com/wilson-eft/wilson/blob/master/.github/workflows/check%2Bdeploy.yaml#L72 evaluated to false. Offending line added by @dvandyk in 3660307.

Hi @DavidMStraub, this line is correct, since it prohibits deployment on all events except a release event. @peterstangl is right, there should be another workflow appear in the list, triggered by a release event. Looking into it.

dvandyk commented 2 years ago

And here we go... I used the wrong event type:

Note: Workflows are not triggered for the created, edited, or deleted activity types
for draft releases. When you create your release through the GitHub browser UI,
your release may automatically be saved as a draft.

Here https://github.com/wilson-eft/wilson/blob/bf8cf0d43b7023ff87649eb2d50245b0106b8847/.github/workflows/check%2Bdeploy.yaml#L8 it should read [published].

peterstangl commented 2 years ago

@dvandyk indeed, I first drafted the release before publishing it. So I actually never "created" it and thus the workflow was not triggered.

dvandyk commented 2 years ago

PR #99 should fix this issue, and another that I noticed while reading the Github Actions documentation.

peterstangl commented 2 years ago

Fixed by @DavidMStraub uploading the release and @dvandyk fixing the workflow in #99.