GitLab badges are not working

[ogarcia]

Are you experiencing an issue with...

shields.io

🐞 Description

It seems that several GitLab badges are not working properly. At least I have detected License and Release.

🔗 Link to the badge

For example, for this GitLab project, the project id is 42779682. The shields shows project not found:

The same applies if you use the project path ogarcia/lesma.

💡 Possible Solution

No response

[chris48s]

I think our GitLab token has expired. There was an email to one of the shared accounts about a week ago saying a GitLab token was about to expire, but I didn't make the connection. These are working locally with no auth
@PyvesB @calebcartwright - do either of you have the credentials to generate a new token? I don't think I have them.

[PyvesB]

https://github.com/badges/shields/blob/master/doc/production-hosting.md suggests @calebcartwright should have them? Unless I've missed something, I haven't found anything on Keybase or elsewhere on my side.

[calebcartwright]

I do, although to the best of my recollection, any token should do. GitLab declined to give us a token with a higher rate limit, and in fairness I don't think rate limiting has been an issue.

Additionally, I don't believe GitLab supports renewing/modifying the expiration date on an existing token so a new one will indeed be needed. I'll try to dig up the credentials (I thought I'd shared them privately in Discord), though anyone of us with a GitLab account should be able to create and provide an alternative token if I'm unable to do this expeditiously.

[chris48s]

Thanks.
Just set the new key. GitLab badges should be working now (or at least coming back as things drop out of cache).
I had not focused that we just have a standard PAT for GitLab. I'll make a note of this in the docs when I get a sec.

[calebcartwright]

Glad to hear it. Let me know if we run into an issues with the token. I think I selected all the relevant scopes we'd need but can't say I'm particularly familiar with them