-
Notifications
You must be signed in to change notification settings - Fork 25
Description
I set up the TagBot in a way that should result in a release with the green "verified" badge from GitHub. However, I just released a newer version of my package and was surprised that the Git tag was not signed.
(git verify-tag returns error: no signature found)
The GPG signing worked as expected in the past months for two earlier releases I made via TagBot. I didn't change any setting for TagBot or anything with the GitHub secrets. So, I wonder whether it could be an issue with TagBot itself.
(In case it is helpful, the link to the package is here: https://github.com/JuliaDiffinDiffs/DiffinDiffsBase.jl)
Update:
I have force pushed a tag that is signed locally to GitHub to replace the unsigned one.
Yet, I am still curious why the GPG sign was not done automatically.