Problem with Package Release

I was trying to release a new version 0.6.1 of View5D.jl.
Everything went smoothly including the Merge:

Yet somehow this release does not seem to appear and also the TagBot in my Repo

was triggered but did not create the release. I do remember that I accidently first made a release by hand in this repo and then deleted it again, before triggering the Bots.
Any ideas what could be the cause and how to fix it?

Yeah, it looks like you already created a tag by hand: Release v0.6.1 · RainerHeintzmann/View5D.jl · GitHub

So then tagbot does not run: TagBot trigger issue · RainerHeintzmann/View5D.jl@c673de5 · GitHub

Maybe you deleted the release but not the tag? So try deleting that tag, then rerunning tagbot by going to TagBot · Workflow runs · RainerHeintzmann/View5D.jl · GitHub and clicking run workflow:

(screenshot from a different repo since the button doesn’t show up for me on your repo since I don’t have access, but I see you do have a workflow_dispatch trigger so you should have the option)

2 Likes

Thanks a lot!! This worked. The Release is now nicely visible in View5D.jl repo.
However, so far it is not updated in the Julia main package list repo. Will this be rechecked regularly or can I re-trigger something there?

1 Like

What are you referring to?

1 Like

Sorry. Bad wording. I meant the main Julia registry. This still does not seem to know about the new release. So I reckon that it also needs a nudge to update?

Indeed. Using

worked and it updated the registry correct. So I guess that it will be in the main registry shortly.

Hi I think I am having a similar problem with AD4SM, I invoked the tag bot but the release was not created, and it says that the tag already exists,

do you know where can I find some info to overcome this issue?

you suggested to delete the tag and restart the tag bot, how can I do that?

thanks in advance!

I found how to delete the old tag, now the TagBot worked fine and the release has been updated! many thanks for these posts!

… finally it trickled through, so the “up” command now fetches the new version. However, the old version was still not marked by the green update arrow.