Fix duplicate Dependabot configuration

[maghuro]

Summary

Fix the Dependabot configuration so both main and dev GitHub Actions update targets are contained in a single valid configuration document.

Problem

The current .github/dependabot.yml declares the top-level version and updates keys twice.

Conceptually it contains:

version: 2
updates:
  - target-branch: main

version: 2
updates:
  - target-branch: dev

Duplicate mapping keys are invalid or ambiguous depending on the YAML parser.

A parser may reject the configuration or treat the later updates key as replacing the earlier one, potentially preventing Dependabot from handling one of the intended target branches.

Fix

Keep a single:

version: 2
updates:

and place both GitHub Actions configurations in the same updates list.

The existing settings for each target branch remain unchanged.

Result

Dependabot has two explicit GitHub Actions update configurations:

• target branch main
• target branch dev

Both retain the existing weekly schedule and grouped action updates.

Scope

This PR only removes the duplicated top-level YAML keys and combines the two existing update entries under one updates list.

No Dependabot schedule, grouping, ecosystem, directory, or target branch is otherwise changed.

[ExtremeFiretop]

This exposed something to me. But this is not the fix I want to implement.

This fix as written would allow dependabot to check both main and dev branches and submit PRs against both, but that is not the intended design and workflow we follow, all PRs including ones from dependabot must come through the dev branch first.

Additionally, having dependabot open PRs against main would conflict with our other workflow called: Check-PRsource.yml.

For now, this will be closed. I will make my own fix to this YML that maintains the intended design, and credit you for the find.

Thanks!

[ExtremeFiretop]

@maghuro

See commit: 58d93df