@@ -88,7 +88,7 @@ follow a slightly different strategy.
8888
8989All Micronaut repos have 2 dependency upgrade checking mechanism:
9090
91- 1 . Dependabot : it has the advantage that it performs dependency upgrades not only on build dependencies, but also on
91+ 1 . Renovate : it has the advantage that it performs dependency upgrades not only on build dependencies, but also on
9292 GitHub Actions workflows. On the other hand, its biggest downside is that it's unable to find newer versions for
9393 those defined in ` gradle.properties ` . It will also send different PRs for the same version upgrade if the artifact ID
9494 is different. For example, if you have ` com.example:client:1.0 ` and ` com.example:server:1.0 ` , and a new 1.1 version
@@ -99,9 +99,9 @@ All Micronaut repos have 2 dependency upgrade checking mechanism:
9999 during weekdays.
100100
101101The consequence of having both approaches in place is that we get multiple dependency upgrade PRs: one created by
102- ` micronaut-build ` via our automation, and one or many (one per dependency) created by Dependabot . When merging those, it
102+ ` micronaut-build ` via our automation, and one or many (one per dependency) created by Renovate . When merging those, it
103103is better to prefer the ` micronaut-build ` ones, if possible, for 2 reasons: a) they attempt to upgrade multiple dependencies
104- in a single PR, which creates less noise in the Git history; b) Once you merge that, Dependabot will react and automatically
104+ in a single PR, which creates less noise in the Git history; b) Once you merge that, Renovate will react and automatically
105105close its own PRs if the dependecy is up-to-date.
106106
107107When an upgrade to a new version arrives, we need to be careful when merging, so that we don't introduce an
@@ -111,7 +111,7 @@ information.
111111
112112Note that if a new version arrives and we are not ready yet to do the upgrade, you need to
113113[ pin the old version] ( https://github.com/micronaut-projects/micronaut-build/#configuration-options ) , because otherwise,
114- Dependabot and our workflow will keep sending PRs. You should also create an issue to upgrade so that it's not forgotten.
114+ Renovate and our workflow will keep sending PRs. You should also create an issue to upgrade so that it's not forgotten.
115115
116116#### Files sync
117117
@@ -126,7 +126,7 @@ template repo will get propagated automatically. The files propagated are:
126126 * ` gradle.yml ` .
127127 * ` release.yml ` .
128128 * ` release-notes.yml ` .
129- * Dependabot configuration (` .github/dependabot.yml ` ).
129+ * Renovate configuration (` .github/renovate.json ` ).
130130* Gradle wrapper.
131131* ` .gitignore ` .
132132* ` ISSUE_TEMPLATE.md ` , ` LICENSE ` , ` MAINTAINING.md ` , ` config/HEADER ` and ` config/spotless.license.java ` .
0 commit comments