tree 0cb8d725432a3cd08522f36c01424dcb930a44aa
parent df0f42318422a94e8e09a5bc26fa5aeae82b45f6
author Jenn Magder <magder@google.com> 1731355490 -0800
committer GitHub <noreply@github.com> 1731355490 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJnMmNiCRC1aQ7uu5UhlAAArfQQAJrDTnMrX0CtxzGTvvtOjOuH
 2c/MvzvwoLagSAGCyvdpaH70ZC7ic789CxtgEw6KpiAo6+JhUsZPU50y51gnn8rp
 i/+VhUwz/TlLDosyBQZ+YqdvKeVrOua7gxu8L3iKufCSoE+EroH5dTEQETdgx2TQ
 LprSbbo6mCoHX1IuhoqJBVF7k3Y1wQPGTz+GzkXMzcPIM2KsXgc4x+sMjlDcJ6yp
 llVqccVwsUjduKt6xPH6W9OhANG+d20ULY86oTsMNntzGk6mScAs1Hw1Il7taor3
 cfhzOZpxXtZt8MMc/Zh69z162ll5x2ET1rzYgG/2bA9UrYZPugizc4Mx6JT964/q
 gGjDnROulfIOoAiv5/QcRSP5Tink8v5v+uOVwnl/WtxlRXziYE5Mv7thXHssA91X
 1Buaic5oMTpn/kHRukM0Ui57cqTElwoJA3q+vEzF3h5WV7NBQheecke9otiUIFOC
 nKVdJUCBNDR4w++VXJKWCzTKgfKRr3LO/a4IGGWgHGKvYpHQ7Kh94eCyS5+ASlum
 bDzjPuX+7agezdL/CCUr0y9xFxE52ienSErPOHmaijViMltwQeso61m4tD8UJ4bd
 P7wxjf33GHV4BdyJZ3Ia5A16HaW3Rxp/oCJbSUyirPINjlyL6NpiLlA/fL4LD6pS
 FAx5RuHQuGlbxaOZxtUw
 =im5w
 -----END PGP SIGNATURE-----
 

Use dependabot multi-directory configuration for Android package updates (#8048)

Follow up to https://github.com/flutter/packages/pull/8036#issuecomment-2465781953.

[Multi-directory config](https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#directories) allows duplicated dependabot configs can be removed in favor of one that specifies multiple directories.  Update Android packages so the same gradle dependencies can be updated all at once across packages.

> The directories option in the dependabot.yml file allows you to apply Dependabot updates to multiple directories at the same time.

It's unclear whether this is a good idea.
> I'm a bit skeptical that grouping all the non-example ones together will be easier in practice, since usually some plugins are fine and some need changes, but I know the current system has some issues too.

https://github.com/flutter/packages/pull/8036#pullrequestreview-2424660637

The consensus seems to be we should try it, and revert or adjust if it makes the current system worse.

Part of https://github.com/flutter/flutter/issues/148098