[drevendev]

Related: #63 (keep issue open until a scheduled Dependabot run is verified).

Goal

Dependabot is configured for release/0.3.0, which does not exist as an upstream branch. The upstream release/0.6.0 branch exists and contains the currently maintained release candidate.

Evidence / change

On release/0.6.0, existing .github/dependabot.yml blob 03ced887bb0326c53d9754fa5a08ea762373cdbe has two stale target-branch: "release/0.3.0" entries. This PR changes only those two entries to release/0.6.0, leaving scheduling (Tuesday weekly), grouping and 7-day cooldown intact.

Source branch commit: f493099e84d3ef25c45a486da620f3dac06aa3cb. Updated file exact readback blob b4eed35b5eb8edf7d54c50dfbb5314db5382f03a; exactly two new target-branch occurrences, no stale target. This is a release-branch PR, not a direct write to master.

Non-goals

No package bumps, version tags, release publishing, workflow overrides, change to unrelated .github files, or promises of completed Dependabot execution.

Acceptance

• Both ecosystems point to the actual upstream release branch.
• Same-head CI and review are green; protected branch procedures observed.
• Post-merge: verify next scheduled Dependabot run and actual PR base; do not treat file text as proof that the service executed. Issue Release automation: Dependabot targets an absent upstream release branch #63 remains operationally open until that provider-side confirmation.

Verification

• GitHub readback of exact branch: passed.
• Local Python suite: not_run (only static YAML text changed; provider CI pending).
• Dependabot scheduled execution: not_run.
• Highest-risk area: intent of release-branch routing; maintainers should confirm that release/0.6.0 is the active dependency-maintenance target while earlier releases finish.

Target: E4

[drevendev]

Reviewed exact head f493099e84d3ef25c45a486da620f3dac06aa3cb against issue #63, upstream release/0.6.0 and CONTRIBUTING.md. One file changed: both obsolete Dependabot targets release/0.3.0 now point to an existing release/0.6.0. Schedule, cooldown and package grouping are untouched. CI run 39169130975 passed Python 3.12, 3.13 and 3.14. No blocking change found for this configuration-only feature-branch PR. Integration may proceed into release/0.6.0, not master. Do not close #63 until a real scheduled Dependabot update against the intended branch is verified; this patch proves configuration, not execution.