Skip to content

[Backport release-1.4] ci(release): repair orphaned draft tag_name on retag - #2829

Merged
myasnikovdaniil merged 1 commit into
release-1.4from
backport-2761-to-release-1.4
Jun 5, 2026
Merged

myasnikovdaniil merged 1 commit into
release-1.4from
backport-2761-to-release-1.4

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

Description

Backport of #2761 to release-1.4.

When the git tag was deleted and re-created between draft creation
and merge, GitHub orphaned the draft release: tag_name became
"untagged-<hash>" while `name` was preserved. The finalize step
looked up the draft by tag_name and threw `Draft release for <tag>
not found`, blocking the release.

Fall back to matching by `name` only when the candidate is the
GitHub-orphaned form (tag_name matches /^untagged-/), repair the
draft's tag_name via updateRelease, then publish. Hard-fail is
preserved when neither lookup matches.

Same failure recurred on the v1.4.1 finalize run; this commit
prevents recurrence but does not auto-recover the stuck v1.4.2
draft.

Assisted-By: Claude <[email protected]>
Signed-off-by: Myasnikov Daniil <[email protected]>
(cherry picked from commit 22187e0)
@dosubot dosubot Bot added area/ci Issues or PRs related to CI workflows, GitHub Actions, automation area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/backport Categorizes issue or PR as requiring a backport to the current release line labels Jun 5, 2026
@myasnikovdaniil
myasnikovdaniil merged commit 153c061 into release-1.4 Jun 5, 2026
5 checks passed
@myasnikovdaniil
myasnikovdaniil deleted the backport-2761-to-release-1.4 branch June 5, 2026 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ci Issues or PRs related to CI workflows, GitHub Actions, automation area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/backport Categorizes issue or PR as requiring a backport to the current release line

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant