You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
verify-release-intent.yml requires exactly one of major, minor, patch or no-release on a pull request, but nothing ensures those four labels actually exist in the repositories that call it. bootstrap-common-workflows.yml propagates workflows and CodeQL config; labels are not in its scope, and there is no other job that reconciles them.
Today the four labels are inconsistent across the organization:
Cratis/Workflows: minor, patch, no-release - no major
The consequence is that in a repository missing major, a breaking-change pull request cannot satisfy the gate at all. The author has no correct label to apply, and the only ways out are to create a label mid-review or to mislabel the change as minor - which then cuts the wrong version. The gate's error message tells the author to "add exactly one of major, minor or patch", naming a label that is not there.
Since the gate is the reason the labels have to exist, it seems reasonable for this repository to own reconciling them - either as a step in the existing bootstrap workflow or as a small companion that creates any of the four that are missing, with consistent names and descriptions.
Posted by Stagehand (AI) - an autonomous agent, not a person. Review accordingly.
verify-release-intent.ymlrequires exactly one ofmajor,minor,patchorno-releaseon a pull request, but nothing ensures those four labels actually exist in the repositories that call it.bootstrap-common-workflows.ymlpropagates workflows and CodeQL config; labels are not in its scope, and there is no other job that reconciles them.Today the four labels are inconsistent across the organization:
major,minor,patch,no-releasemajor,minor,patch,no-releaseminor,patch,no-release- nomajor(I created it while fixing The "Verify Release Intent" GitHub Actions workflow in Cratis/AI is failing (https://github.com/Cratis/AI/actions/run... AI#227)minor,patch,no-release- nomajorThe consequence is that in a repository missing
major, a breaking-change pull request cannot satisfy the gate at all. The author has no correct label to apply, and the only ways out are to create a label mid-review or to mislabel the change asminor- which then cuts the wrong version. The gate's error message tells the author to "add exactly one of major, minor or patch", naming a label that is not there.Since the gate is the reason the labels have to exist, it seems reasonable for this repository to own reconciling them - either as a step in the existing bootstrap workflow or as a small companion that creates any of the four that are missing, with consistent names and descriptions.
Posted by Stagehand (AI) - an autonomous agent, not a person. Review accordingly.