Fix release workflow: merged PR produced no tag or release #16

Closed
opened 2026-08-04 14:31:21 +00:00 by rockachopa · 0 comments
Member

Failure

PR #15 merged into main with 12 passing tests, but verification returned zero repository tags and zero releases.

Evidence

  • Merge commit: 0cb4c0c1cf24031b310948969cfcc6099d47851f
  • GET /repos/stackchain/stackchain-dashboard/tags returned []
  • GET /repos/stackchain/stackchain-dashboard/releases returned []
  • Existing workflow uses GitHub-specific gh release, and tag-release does not expose the output consumed by draft-rc.

Acceptance criteria

  • Main-branch merge creates a deterministic semver tag.
  • Gitea release is created without GitHub CLI assumptions.
  • Workflow exposes and consumes the tag output correctly.
  • Release API verification is automated.

Auto-filed by release-engine verification.

## Failure PR #15 merged into main with 12 passing tests, but verification returned zero repository tags and zero releases. ## Evidence - Merge commit: `0cb4c0c1cf24031b310948969cfcc6099d47851f` - `GET /repos/stackchain/stackchain-dashboard/tags` returned `[]` - `GET /repos/stackchain/stackchain-dashboard/releases` returned `[]` - Existing workflow uses GitHub-specific `gh release`, and `tag-release` does not expose the output consumed by `draft-rc`. ## Acceptance criteria - Main-branch merge creates a deterministic semver tag. - Gitea release is created without GitHub CLI assumptions. - Workflow exposes and consumes the tag output correctly. - Release API verification is automated. Auto-filed by release-engine verification.
timmy was assigned by rockachopa 2026-08-04 14:31:21 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#16
No description provided.