Auto-merge Renovate pull-requests for patch/minor/digest

[NimJay]

Terminology

• From semver.org (major.minor.patch):
  • major = incompatible API changes
  • minor = new functionality & backwards compatible
  • patch = bug fixes & backwards compatible
• digest = similar to pull-request #1426

Background

• Most of the pull-requests merged into main come from Renovate Bot (dependency updates).
• Most of these updates are not major updates.
• The review process for a non-major updates is: if the CI checks are passing, merge the pull-request.

Feature Request

• Renovate Bot updates should be auto-merged if the following conditions are met:
  1. the update is one of: patch; minor; digest
  2. the relevant CI tests are passing
• For now, major updates should go through a manual review.
  • We have experienced breakages of Online Boutique functionality because of major Renovate Bot updates (e.g., when pino was updated).
  • We could auto-merge major updates too once we have thorough end-to-end tests of most of Online Boutique (e.g., U.I. tests).

Additional Notes

• This will free up a lot of the time that our team spends on reviewing Online Boutique pull-requests.

[gitsan13]

Hi @NimJay
I would like to give this issue a try. Can you please assign me to it?

[NimJay]

Hi @gitsan13,

First, thank you for your interest in contributing.
This issue (about auto-merging Renovate pull-requests) is more appropriate for someone with admin access to this GitHub repository.

If you'd like to work on something, I recommend: #693
But #693 is a big task because it involves multiple microservices.
So you could try #693 for a specific microservice (e.g., for the frontend — is alpine:3.17.0 the smallest base image we can use, or it there something smaller)?

[minherz]

@bourgeoisor for your tracking

[bourgeoisor]

Done here: #1835