[Bug]: Publication looks up draft Releases using a published-only tag endpoint #19

Affected module or tool

GoReleaser publication adapter / draft Release discovery.

Version or commit

Full v0.1.0 preparation PR #16, publication commit 34fcc751355a2b29bca393748139ff96dd8bbf2a.

Environment

Hosted Ubuntu publication workflow with GoReleaser OSS v2.18.2 and the built-in GitHub token.

Minimal reproduction

Start the authorized full batch after all required checks pass. GoReleaser creates the root v0.1.0 draft, then the adapter requests GET releases/tags/v0.1.0.

Expected behavior

Discover and validate the matching draft, verify its public Go consumer, and finalize that draft with GoReleaser before continuing to dependent modules.

Actual behavior

Publication run https://github.com/rambow-cloud/powertools-lambda-go/actions/runs/37205386202 failed with HTTP 404 immediately after successful draft creation. Authenticated release listing contains draft ID 403031893 tagged v0.1.0, and the real v0.1.0 tag points to the exact approved SHA. GitHub's tag lookup endpoint returns published releases, so drafts must be located through the authenticated release list. No tag should be rewritten and the tracking issue must remain open while recovery continues.

Acceptance criteria or proposed fix

Use a published-release lookup plus authenticated draft-list fallback for publication conflict checks and resume. Reject duplicate matching drafts. Preserve exact notes, tag targets, version, consumer gates, and GoReleaser ownership of finalization. Make fake/local GitHub fixtures reflect draft-by-tag 404 behavior, and verify draft creation/finalization/resumption with the real pinned CLI before recovering the unchanged batch.