🏷️: bump to rc2 for new release to trigger release workflow #485
Conversation
|
the v4.0.0rc1 tag was already made with the first attempt at a release candidate (release workflow failed) -- the new GitHub release tag would have to be rc2. We could make the release rc2 on GitHub and rc1 on pyPI but that doens't make any sense. |
|
@MrCordeiro let me know if that makes sense i'll wait to merge this time. |
|
I guess I might be mistaken that you can't edit the tag on the GitHub Release. It seems like in the UI that the platform lets you edit it. If that's the case then you might be right and we can try that route. |
|
never mind; it looks like you can only edit the notes for the release not the tag itself. We good @MrCordeiro ? |
|
PS it looks like i tagged the wrong commit/branch in my terminal because i had forgotten that GH tags releases for us and thats why the workflow failed, not the syntax like i thought -- that was my mistake. And why i'm test running with release candidate. I tried to be careful; not sure how i tagged the wrong commit! |
|
I'll take your deleted comment as a 'good to go' -- let's touch base tomorrow about the full release; maybe you can handle it @MrCordeiro so i dont mess it up 😉 |
|
PS another reason why i'm stumbling a little bit here is that i usually manage releases through python-semantic-release which automates much of the process. If i get the time i'd like to submit a PR implementing this to lessen maintenance burden just a little bit but obviously would need your sign off @MrCordeiro |
No description provided.