chore: remove rennovate #314
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Compliance Checks
Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.
Issue Reference
In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. We are closing this pull request for now but you can update the pull request description and reopen the pull request.
The check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.
There was a problem hiding this comment.
😄 I haven't had email notifications enabled in years... and then for Dependabot/Renovate had to automate completely unsubscribing from them automatically: https://github.com/JoshuaKGoldberg/prune-github-notifications. I'd completely forgotten this repo has these enabled!
@Richienb in other repos I've disabled patch updates, which got rid of most (but not all) of the updates:
"patch": { "enabled": false },WDYT?
There was a problem hiding this comment.
Gonna try this tip renovatebot/renovate#1254 (comment)
{ "enabled": false }
I have received hundreds of dependency emails for this repository alone.
I don't think it is useful because most updates change the lockfile, but the lockfile is never published on npm.
The alternative to removing rennovate is to restrict it to only recommend updates to dependencies in
package.json, or only security critical dependencies.