TagBot produces no new tag for a registered package

[andreasvarga]

I registered a new version v0.6.0 of my package PeriodicSystems and the new version appears in the registry (see here). However, after 19 hours, the expected new tag v0.6.0 for the new version has not been produced. I know I can do the tagging manually, but I would like to continue to rely on TagBot, which until now worked every time as expected.

[ericneiva]

Hi, @andreasvarga, your TagBot workflow is giving a GitHub 502 exception, see here. Other people like me are experiencing the same issue, unfortunately, I don't know how to fix it.

[andreasvarga]

Thanks for the hint. I any way to launch TagBot once again or I have to proceed manually?

[andreasvarga]

I executed TagBot once again following this advice, with the same result (GitHub error 5xx) and no generated tag. Apparently many people face this problem. I wonder if there is chance to avoid this issue, or we should abandon completely using TagBot?

[ericneiva]

@andreasvarga I re-run all jobs of my TagBot trigger issue action that failed and it generated the tag. Have you tried that too on your own trigger issue?

[andreasvarga]

I already made the new tag manually (just a few minutes before your last comment)! I am not sure if it is a good idea to re-run all-jobs now. But, I am preparing a new release and perhaps this would be an opportunity to check your fix if new troubles occur. Thanks.