Thanks for the heads-up!
Unfortunately, this is a known bug in our CI/CD signing repo script logic that doesn’t correctly choose which cache to invalidate after the repo is automatically updated.
I’ve fixed it manually, and everything should work now. I’m also working on figuring out why it doesn’t happen correctly automatically.