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
Note to ourselves: we should make the PyPi (and conda-forge) publishing be automatically triggered from a CI step in github, once the repo is tagged with something like vX.Y.Z.
#96
Open
mjuric opened this issue
Nov 14, 2023
· 0 comments
We should make the PyPi (and conda-forge) publishing be automatically triggered from a CI step in github, once the repo is tagged with something like vX.Y.Z.
It would ensure pip+conda releases are always consistent with the code on github (and make the whole release process much easier -- just tag, push & let the CI do the rest).
We should make the PyPi (and conda-forge) publishing be automatically triggered from a CI step in github, once the repo is tagged with something like
vX.Y.Z
.It would ensure pip+conda releases are always consistent with the code on github (and make the whole release process much easier -- just tag, push & let the CI do the rest).
Originally posted by @mjuric in #94 (comment)
The text was updated successfully, but these errors were encountered: