-
Notifications
You must be signed in to change notification settings - Fork 3
build: release-workflow - Add approval and concurrency gates #780
Copy link
Copy link
Open
Labels
area:automationarea:buildsmigrate:area:automationAutomation workflows and agentsAutomation workflows and agentsmigrate:area:ciBuild and CI pipelinesBuild and CI pipelinesmigrate:priority:importantMust-do high priorityMust-do high prioritymigrate:status:needs-planningAwaiting planning / scopingAwaiting planning / scopingmigrate:type:buildBuild & CIBuild & CIpriority:importantstatus:needs-planningtype:build
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
area:automationarea:buildsmigrate:area:automationAutomation workflows and agentsAutomation workflows and agentsmigrate:area:ciBuild and CI pipelinesBuild and CI pipelinesmigrate:priority:importantMust-do high priorityMust-do high prioritymigrate:status:needs-planningAwaiting planning / scopingAwaiting planning / scopingmigrate:type:buildBuild & CIBuild & CIpriority:importantstatus:needs-planningtype:build
Type
Fields
Priority
High
Build/CI Summary
The current release workflow can still race, and the live publish path is too easy to reach without a strong workflow-level gate.
Steps / Checklist
Acceptance Criteria
Additional Context
.github/projects/active/release-agent-hardening/openspec-strict/children/01-2-task-workflow-hardening-and-approval-gates.mdReferences
Definition of Ready (DoR)
Definition of Done (DoD)