Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release tags not being created? #173

Closed
stevengj opened this issue Jul 4, 2023 · 8 comments
Closed

release tags not being created? #173

stevengj opened this issue Jul 4, 2023 · 8 comments

Comments

@stevengj
Copy link
Member

stevengj commented Jul 4, 2023

For some reason, no releases are being tagged by @JuliaRegistrator, since version 1.1. @fingolfin last updated TagBot in #165.

@JuliaMath JuliaMath deleted a comment from JuliaRegistrator Jul 4, 2023
@quinnj
Copy link
Collaborator

quinnj commented Jul 4, 2023

I've had to redo the DocumenterTools.genkeys() process for several of my repos; I think there may have been a bunch of keys reset at some point automatically by GitHub.

@fingolfin
Copy link
Contributor

Yes, the SSH_KEY needs to be setup. Please follow the instructions at https://github.com/JuliaRegistries/TagBot#ssh-deploy-keys.

@fingolfin
Copy link
Contributor

After you have done that you can hopefully generate the missing tags by going to https://github.com/JuliaMath/DecFP.jl/actions/workflows/TagBot.yml and then (if you have sufficient admin rights) select the "Run workflow" popup button; in there, set the "lookback" value high enough that it cover the missing commits -- it is given in days, the default is 3, but the 1.2 release was 2021-11-23, so I guess you need something like ... 800 or so, to be on the safe side cough. Disclaimer: I am not sure how well that works, and if it will detect all "missing" releases in one go, or if you have to maybe run this multiple times...

@stevengj
Copy link
Member Author

stevengj commented Jan 5, 2024

Should be fixed now, thanks!

@stevengj stevengj closed this as completed Jan 5, 2024
@stevengj
Copy link
Member Author

stevengj commented Jan 5, 2024

But it doesn't look like it worked to create the 1.2 and 1.3 release tags retroactively :sad:

@fingolfin
Copy link
Contributor

The run produced a "GitHub returned a 5xx error code". Maybe that day range is just to big. The last release was in July (?) so maybe try with something like 210 days instead?

@fingolfin
Copy link
Contributor

... or just make another release ;-)

@stevengj
Copy link
Member Author

stevengj commented Jan 6, 2024

I tried 210 days, no dice.

It's not a huge deal, we can just wait until the next release (assuming it works then).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants