Merge Confidence Workflows

Introduction

Merge Confidence Workflows 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 repositories running on Mend Renovate Cloud 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 Sematic Versioning (“SemVer”). 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.

• Although maintainers will attempt to determine what “backwards compatible” means, there are cases where inadvertent changes in behaviour may be included in what they believe is a “backwards compatible” change

• Not all ecosystems use SemVer as their versioning scheme, nor does the Major.Minor.Patch version mean that a package is actually using SemVer

• We recommend minor and patch versions be tested with Merge Confidence, as they should be backwards compatible, but may not be.

• Most major versions can be assumed to not have backwards compatibility, but using Merge Confidence could give greater confidence in a major version upgrade if others in the ecosystem have found it to work.

• Merge Confidence Workflows can perform more actions than just automatic merging. It can also include PR suppression, and more.

Examples

For examples on how to implement Merge Confidence Workflows, please refer to our Renovate Merge Confidence Workflows Implementation Examples.