Set up Dependabot about android-fhir HOT 5 CLOSED

PR #2196 alone might actually not suffice (but is probably still required); I suspect both that one to make a start but then also a solution for #2194 is required... let's just try and see!

from android-fhir.

have you seen this https://medium.com/@vladyslav.hontar/dependabot-in-action-d9b56b2be86c?

from android-fhir.

Re-opening, this is NOK, see e.g. https://github.com/google/android-fhir/runs/17467825398:

Dependabot couldn't parse the config file at .github/dependabot.yaml. The error raised was:

(<unknown>): did not find expected key while parsing a block mapping at line 3 column 1

from android-fhir.

Re-opening, this is NOK, see e.g. https://github.com/google/android-fhir/runs/17467825398:

This doesn't happen anymore (after #2234).

But https://github.com/google/android-fhir/settings/security_analysis still says Dependabot version updates. Allow Dependabot to open pull requests automatically to keep your dependencies up-to-date when new versions are available. as if this wasn't configured yet.

have you seen this https://medium.com/@vladyslav.hontar/dependabot-in-action-d9b56b2be86c?

This looks like what we may have to do... I'll try this out some time.

from android-fhir.

Duh, e.g. https://github.com/google/android-fhir/runs/17521930462 (et al) now fails with:

Your .github/dependabot.yaml contained invalid details
Dependabot encountered the following error when parsing your .github/dependabot.yaml: The property '#/' contains additional properties ["open-pull-requests-limit"] outside of the schema when none are allowed.

At this point, I'm just going to remove that open-pull-requests-limit thing, for now; see #2242.

from android-fhir.