Address Automated Bots Pull Requests

[vaporwavie]

Problem

Currently, our repo has a considerably high amount of PRs made by an automated bot, mostly coming from Renovate. While important to detect and propose version updates, it doesn't necessarily cover the upgrade factors, meaning that breaking changes can occur by simply bumping the lib version. The lack of sanity checks makes those PRs somewhat dangerous from a maintenance perspective, and requires additional layers of verification from the maintainers (either for merging/closing)

Solution

Our next steps would be doing research on how this can be either circumvented or completely replaced. Both are heavy-lifts and may require milestones on doing so.

Usage examples

No response

Dependencies

No response

References

@matheusps proposed Taze as a potential alternative to our current scenario.