Repo: 8.27.0 release was not published to npm

[controversial]

Suggestion

The v8.27.0 release that was published to the changelog and tagged from 3efd99e is not published to npm, where the latest release is still 8.26.1; is this intentional or a mistake?

Additional Info

No response

[kirkwaiblinger]

Yeah, this came up in the discord as well: https://discord.com/channels/1026804805894672454/1084238921677946992/1351881633074118666

I noticed something was weird with f07bdcf, but not sure whether that's a cause or effect 🤔

[kirkwaiblinger]

But, yeah, definitely not intentional!

[bradzacher]

This is an issue caused by our token rotation in response to the security incident. We'll get it published soon.

[bradzacher]

Release is now up on npm