Describe the feature
Same as vert-x3/vertx-micrometer-metrics#267
Creating a dedicated discussion to define the requirements
Should it only be graphql updates?
For example, we have other dependencies that can benefit from such automation. Example: #2758
Test dependencies may also benefit:
|
<junit5.version>5.7.0</junit5.version> |
|
<assertj.version>3.15.0</assertj.version> |
|
<truth.version>1.1.3</truth.version> |
We already have a dependabot configuration here
|
version: 2 |
|
updates: |
|
- package-ecosystem: "maven" |
|
directory: "/" |
|
schedule: |
|
interval: "daily" |
although it is not using advanced setup. This may be the reason of the perceived noise
Contribution
Yes. Me (@yeikel )
Describe the feature
Same as vert-x3/vertx-micrometer-metrics#267
Creating a dedicated discussion to define the requirements
Should it only be graphql updates?
For example, we have other dependencies that can benefit from such automation. Example: #2758
Test dependencies may also benefit:
vertx-web/vertx-web-api-service/pom.xml
Lines 16 to 18 in 1c77cbe
We already have a dependabot configuration here
vertx-web/.github/dependabot.yml
Lines 1 to 6 in 1c77cbe
Contribution
Yes. Me (@yeikel )