Bug: Dependabot PRs target main instead of Dev_new_gui — creates stale-base diffs

[mrveiss]

Problem

Dependabot PR #2417 (pip group bump) targeted main, which was 399 commits behind Dev_new_gui. The PR showed 100+ changed files when only 5 requirements files actually changed, because the base branch was stale.

Root Cause

.github/dependabot.yml targets main as the base branch, but all active development happens on Dev_new_gui.

Impact

• PRs are unmergeable without massive conflict resolution
• Diff is misleading — shows hundreds of unrelated files
• Had to cherry-pick the single actual commit instead of merging the PR

Suggested Fix

Update .github/dependabot.yml to target Dev_new_gui:

target-branch: "Dev_new_gui"

Discovered During

v0.2.0 release preparation — PR #2417 closed, commit cherry-picked instead

[mrveiss]

Fixed in PR #2473 (merged). Added target-branch: Dev_new_gui to all Dependabot entries.

[mrveiss]

Investigated: .github/dependabot.yml already has target-branch: "Dev_new_gui" for all 5 ecosystem entries (pip x3, npm, github-actions). Config is correct. If PRs still target main, this is a GitHub-side caching issue — try re-enabling Dependabot in repo settings or pushing a whitespace change to the config file to force a re-read.