Repository navigation
Release automation: Dependabot targets an absent upstream release branch #63
Description
.github/dependabot.yml targets release/0.3.0, but that branch currently exists only in the contributor fork. The upstream repository has release/0.2.0 and master; the pending 0.3/0.4 release PRs target master from the fork.
Dependabot's configured upstream target must exist. A new release pin in documentation does not create its branch or publish its tag.
Acceptance: the maintainer establishes the active upstream release branch and retargets both GitHub Actions and pip updates, or explicitly chooses default-branch maintenance and reconciles CONTRIBUTING.md. Confirm the scheduled update runs against that actual branch after the prepared releases land.
Kept separate from feature implementation because fork write access cannot establish an upstream release branch.
Activity
fix: retarget Dependabot to existing 0.6 release branch (#63)
Merge pull request #79 from drevendev/claude/dependabot-target-releas…
drevendev commentedon Oct 18, 2026
Maintainer implementation update — 2026-10-19
The owner-approved, bounded configuration repair for this issue has been merged into the existing upstream
release/0.6.0branch:22a2894057d9b1bc003efe4ef932ed4de601e26b.target-branchentries in.github/dependabot.ymlnow sayrelease/0.6.0(exact branch file readback).Do not close #63 yet: the remaining acceptance criterion is to observe an actual scheduled Dependabot update routed to that branch; it has not yet been run/verified. If the active release target changes again, the maintained config must follow. No claim that 0.6.0 has shipped or that blocked older release/Integrity work is complete.