Skip to content

Merge dependabot configurations into a multi-ecosystem group #77

Closed

Description

@freakboy3742

What is the problem or limitation you are having?

This project's dependabot configuration currently defines multiple "ecosystems" to be updated. As currently configured, these are run as separate updates.

We can minimize the number of updates by merging multiple updates into a single "multi-ecosystem group". This results in a single dependabot update.

Describe the solution you'd like

We should migrate the configuration of this repository to use a single "dependencies" multi-ecosystem group, rather than multiple independent groups.

The briefcase-template repository contains an example of how a multi-ecosystem configuration is configured.

Describe alternatives you've considered

Leave the configurations as single-ecosystem updates.

Additional context

Activity

  1. added
    enhancementNew features, or improvements to existing features.
    good first issueIs this your first time contributing? This could be a good place to start!
    on Jul 17, 2026
  2. moved this from To triage to Ready in BeeWare Planningon Jul 17, 2026
  3. AlexVerrico commented on Aug 30, 2026

    @AlexVerrico
    Contributor

    Looking at this at PyConAU2026

  4. moved this from Ready to In progress in BeeWare Planningon Aug 30, 2026
  5. moved this from In progress to Done in BeeWare Planningon Aug 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew features, or improvements to existing features.good first issueIs this your first time contributing? This could be a good place to start!

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions