Skip to content

Release-intent gate requires labels that repositories are not guaranteed to have #84

Closed

Description

@cratis-direct

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:

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.

Status

State: Done — Bootstrap succeeded; create-only correction added Orleans major; Orleans and Stage readback confirmed all four labels; issue closed.
Branch: stage-422-atomic-execution (#211)
Scope: Bootstrap creates any missing major/minor/patch/no-release labels in repos that get the release-intent gate; never edits or deletes existing labels
Delivered: Nothing yet.
Remaining: To be confirmed.
Follow-ups: None.

Activity

  1. added theissue type on Sep 1, 2026
  2. reopened this on Oct 22, 2026
  3. self-assigned this
    on Oct 25, 2026
  4. woksin commented on Oct 25, 2026

    @woksin
    Contributor

    Delivered in #211; Bootstrap Common Workflows run 40148584886 succeeded. Bootstrap now creates missing release-intent labels in eligible releasing repositories without editing existing labels. A read-only inventory of all 34 accessible ignored repositories found 21 confirmed releasing repositories: only Orleans lacked a label. The authorized create-only correction added Orleans major (bfdadc); readback confirmed all four labels in Orleans and Stage. Existing labels, workflows and bootstrap ignore lists were unchanged. Chronicle.Wolverine has no detected release-action invocation or enabled release-intent gate, so no labels were added there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions