Repository navigation
Accept native qualified CI workflow paths in release proposals #526
Description
Activity
- added a commit that references this issue
on Oct 5, 2026 🤖 Generated by the Agentic Engineer
Delivered by #529 at signed merge 52e20bf. The current-head required checks and substantive review gates were complete before merge. Fresh protected-main fetch and immutable blob comparisons verified all eleven changed files match the reviewed implementation. Native command and workflow assessment controls exercised the active issue requirements. Production marketplace publication remains explicitly opt-in and is not claimed by these fixes.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Effort
None yet
Projects
- Status
Problem
A valid successful current-main CI observation is accepted with the plain workflow path but refused when GitHub supplies the same workflow qualified by main or refs/heads/main. The merged-release preparation command already accepts these exact forms.
Reproduced against reviewed 739d01b using the actual command and isolated offline fixtures. This is one defect family; related input variants belong to this issue.
Proposed direction
Use the same bounded workflow identity forms for proposal assessment while retaining exact repository, event, branch, commit and successful-completion requirements.
Acceptance criteria
Plain and both native main-qualified paths prepare the same proposal. Other workflows, refs, events, incomplete runs and stale commits remain rejected.
Size: Small.
Part of #101.