ci: add dependabot config (gradle + github-actions), mirroring Netflix/zuul - #1629
Open
kobihikri wants to merge 1 commit into
Open
ci: add dependabot config (gradle + github-actions), mirroring Netflix/zuul#1629kobihikri wants to merge 1 commit into
kobihikri wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, and thank you for Eureka.
Small governance add: this repo has no
.github/dependabot.yml, so neither Gradle dependencies nor the workflow actions ever get automated update PRs. Your sister repo Netflix/zuul runs exactly this config (gradle + github-actions) and merges its dependabot bumps routinely — this PR mirrors it, atweeklyrather than zuul'sdailyto respect this repo's slower merge cadence.Context that motivated it: eureka's client dependency set has a number of long-open version-bump asks (e.g. #1584, #1483, #1445) — automated PRs won't fix policy questions, but they remove the manual overhead for the routine bumps.
README asks for an issue first for non-trivial changes — this is a 10-line additive config file, so I hoped it qualifies as trivial; happy to convert to an issue-first discussion if you'd rather.
For transparency: I used AI assistance to spot and draft this; I verified the missing config and zuul's precedent myself.