Allow auto-merging for Renovate's patch updates

[jinmayamashita]

Pull Request Checklist

• [x] I have checked that this pull request is not a duplicate of a pre-existing pull request
• [x] I have self-reviewed my changes
  • [x] There are no spelling mistakes
  • [x] There are no remaining debug log prints (i.e. console.log())
  • [x] Comments were written for complex code
• [x] I have checked that all tests are passing (for bug fixes and enhancements)
  • [x] CLI Test (npm run test:cli)
  • [x] Unit Test (npm run test:modules)
  • [x] E2E Test (npm run e2e)
• [x] I have added and/or modified relevant tests for my changes (for bug fixes and enhancements)
• [x] I have added and/or modified relevant documentations for my changes (if necessary)

Description

We decided to allow auto-merging for Renovate's patch updates.

Context

On August 23rd, I discussed with @ptrkdan about the issue of too many Renovate PRs piling up, making it difficult for people to manage them. We agreed that maintainers should directly review minor and major updates for now, but we'll allow auto-merging for patch updates.

Notes

Maintainers will review the PRs for major and minor updates.

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: bd9617263de59e3de97990c29d268c2200113058

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR