ci(release): repair orphaned draft tag_name on retag by myasnikovdaniil · Pull Request #2761 · cozystack/cozystack

myasnikovdaniil · 2026-05-28T07:01:20Z

What this PR does

When a release-cut PR is merged after the underlying git tag was deleted and re-created (e.g. the release branch was force-updated between the initial tag push and the merge), GitHub orphans the corresponding draft release — its tag_name becomes untagged-<hash> while name is preserved.

The "Publish draft release" step in pull-requests-release.yaml looks up the draft strictly by tag_name === tag and throws Draft release for <tag> not found, blocking the release. Observed on run #26558920814 cutting v1.4.2, and the same error fired on the earlier v1.4.1 finalize run.

This change adds a fallback: when the primary lookup misses, search for a draft where name === tag and tag_name matches /^untagged-/. If found, repair the draft's tag_name to the real tag via updateRelease before publishing, so the released artifact correctly points at the git tag created earlier in the same job. The strict-fail path is preserved when neither lookup matches.

The fix is forward-only and does not auto-recover the currently stuck v1.4.2 draft — that needs a one-time manual tag_name patch + job re-run, or publishing the draft via the GitHub UI.

Release note

ci(release): the release-finalize workflow now repairs an orphaned draft release (tag_name == `untagged-<hash>` after a tag delete + re-create) by re-linking it to the actual tag before publishing.

Summary by CodeRabbit

Chores
- Improved the robustness of the release publication process to handle edge cases when locating draft releases, ensuring more reliable and consistent release deployments.

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]>

gemini-code-assist · 2026-05-28T07:01:26Z

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

coderabbitai · 2026-05-28T07:01:37Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5fce15ff-e05b-4266-9bfa-b6e70b7f6b3b

📥 Commits

Reviewing files that changed from the base of the PR and between 8afb99b and 22187e0.

📒 Files selected for processing (1)

.github/workflows/pull-requests-release.yaml

📝 Walkthrough

Walkthrough

The release workflow's draft publication step now robustly handles edge cases where GitHub changes a draft's tag_name to untagged-<hash> while preserving the release name. The script first attempts to locate the draft by exact tag_name match, then falls back to searching for orphaned drafts by name and repairs them before publishing.

Changes

Draft Release Selection Robustness

Layer / File(s)	Summary
Draft release location with orphan recovery `.github/workflows/pull-requests-release.yaml`	Draft selection logic now searches by `tag_name` first, then handles orphaned drafts by matching `name` and repairing the `tag_name` field via `updateRelease` before using the draft for subsequent publishing steps.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A draft once orphaned, lost its name,
GitHub tagged it with a hash—so strange!
But now our workflow, wise and keen,
Finds what was lost, and heals the seam,
Restoring tags with gentle care. 📋✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and specifically describes the main change: repairing an orphaned draft's tag_name during release re-tagging.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch fix/finalize-untagged-draft

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

github-actions · 2026-06-05T08:54:18Z

Successfully created backport PR for release-1.4:

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

github-actions · 2026-06-05T08:54:18Z

Successfully created backport PR for release-1.3:

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

… retag (#2829) # Description Backport of #2761 to `release-1.4`.

… retag (#2830) # Description Backport of #2761 to `release-1.3`.

myasnikovdaniil requested review from IvanHunters, Andrey Kolkov (androndo), Andrei Kvapil (kvaps), Aleksei Sviridkin (lexfrei), Timofei Larkin (lllamnyp) and Kirill Ilin (sircthulhu) as code owners May 28, 2026 07:01

github-actions Bot added area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) size/S This PR changes 10-29 lines, ignoring generated files labels May 28, 2026

dosubot Bot added area/ci Issues or PRs related to CI workflows, GitHub Actions, automation kind/bug Categorizes issue or PR as related to a bug labels May 28, 2026

myasnikovdaniil self-assigned this May 28, 2026

IvanHunters approved these changes Jun 3, 2026

View reviewed changes

myasnikovdaniil added kind/backport Categorizes issue or PR as requiring a backport to the current release line kind/backport-previous Categorizes issue or PR as requiring a backport to the previous release line labels Jun 5, 2026

myasnikovdaniil merged commit 26574f0 into main Jun 5, 2026
18 checks passed

myasnikovdaniil deleted the fix/finalize-untagged-draft branch June 5, 2026 08:54

This was referenced Jun 5, 2026

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

Merged

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

Merged

myasnikovdaniil added a commit that referenced this pull request Jun 5, 2026

[Backport release-1.4] ci(release): repair orphaned draft tag_name on…

153c061

… retag (#2829) # Description Backport of #2761 to `release-1.4`.

myasnikovdaniil added a commit that referenced this pull request Jun 5, 2026

[Backport release-1.3] ci(release): repair orphaned draft tag_name on…

4c7443e

… retag (#2830) # Description Backport of #2761 to `release-1.3`.

coderabbitai Bot mentioned this pull request Jun 29, 2026

feat(release): immutable tags & rc→stable promotion (#2677) #3017

Merged

Navigation Menu

Repository navigation

ci(release): repair orphaned draft tag_name on retag - #2761

ci(release): repair orphaned draft tag_name on retag#2761
myasnikovdaniil merged 1 commit into
mainfrom
fix/finalize-untagged-draft

myasnikovdaniil commented May 28, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

gemini-code-assist Bot commented May 28, 2026

Uh oh!

coderabbitai Bot commented May 28, 2026 •

edited

Loading

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

Uh oh!

github-actions Bot commented Jun 5, 2026

Uh oh!

github-actions Bot commented Jun 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

myasnikovdaniil commented May 28, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What this PR does

Release note

Summary by CodeRabbit

Uh oh!

gemini-code-assist Bot commented May 28, 2026

Uh oh!

coderabbitai Bot commented May 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

Uh oh!

github-actions Bot commented Jun 5, 2026

Uh oh!

github-actions Bot commented Jun 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

myasnikovdaniil commented May 28, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented May 28, 2026 •

edited

Loading