Merge Confidence Workflows

Introduction

Smart Merge Control is a feature that is a part of any paid Mend Renovate solution, which allows customers to configure certain Renovate actions based off of a certain “confidence level” concerning a certain dependency version.

Confidence Levels

Mend determines this “confidence level” by:

• Gathering testing data on open source repositories that have made the same upgrade.

• Determining how many repositories have had their tests pass while still making the upgrade.

• Determining what level of confidence this PR should have that the upgrade will succeed.

Here’s some things to keep in mind:

• Most library versioning uses SemVer versioning. This means that each version follows the scheme: Major.Minor.Patch where:

  • Major is any backwards incompatible API changes.

  • Minor is any functionality that is added, that also is backwards compatible.

  • Patch is any backwards compatible bugfixes.

• Most minor and patch versions are the updates that should be tested with Smart Merge Confidence. Most major patch versions can be assumed to not have backwards compatibility.

• Smart merge control can perform more actions than just automatic merging. It can also include PR suppression, and more.

For examples on how to implement Smart Merge Control, please refer to our Renovate Smart Merge Control Implementation Examples.