@gtoison Ok both are back. Do you know how this is released / used? Not familiar with it other than it was out of date and didn't have renovate on it and dependabot had previously given up.

Most users get the plugin through the SonarQube marketplace. Once a version is published on Maven central we need to make a PR like SonarSource/sonar-update-center-properties#448 to get the new version approved.
The PR is generated a part of the release process by the GitHub Action that's inside the project.
The process is described here: https://github.com/spotbugs/sonar-findbugs/blob/master/RELEASE_PROCEDURE.md

That action has many dependencies and they are updated quite frequently. Considering how rarely it is used I did not see much value in constantly keeping up to date, so I had disabled dependabot. Due to my ignorance (I don't know Typescript) I'm also unsure if it is even working because the actual code running in the action is a transpiled index.js but these renovate PR do not update that file.

In my experience most of the java dependencies updates for this project require a bit more that changing a version number (running some scripts, fixing some tests, etc.), so I'm not 100% sold on the value of renovate (for this particular project) either. But I'd be happy to be proven wrong so I enabled renovate to give it another try