Skip to content

fix(ci): provide tag metadata for desktop release publish#38

Merged
braedonsaunders merged 1 commit intomainfrom
codex/fix-release-tag-requirement
Feb 24, 2026
Merged

fix(ci): provide tag metadata for desktop release publish#38
braedonsaunders merged 1 commit intomainfrom
codex/fix-release-tag-requirement

Conversation

@braedonsaunders
Copy link
Owner

Summary

  • add optional workflow_dispatch input release_tag
  • compute release metadata in publish job:
    • use release_tag when provided
    • otherwise default to desktop-v<packages/desktop/package.json version>
  • pass tag_name, name, and target_commitish to softprops/action-gh-release

Why

The publish step failed with:
GitHub Releases requires a tag

Manual workflow runs are usually on a branch ref (for example main) and do not provide a tag context by default. This ensures release creation always has a valid tag.

@braedonsaunders braedonsaunders merged commit f1f2de4 into main Feb 24, 2026
1 check passed
@braedonsaunders braedonsaunders deleted the codex/fix-release-tag-requirement branch February 24, 2026 00:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant