Skip to content

馃悰 fix strict stale plan handling - #54

Merged
clubanderson merged 1 commit into
mainfrom
fix-strict-stale-49
Sep 24, 2026
Merged

clubanderson merged 1 commit into
mainfrom
fix-strict-stale-49

Conversation

@clubanderson

Copy link
Copy Markdown
Member

Summary

  • add plan.strict_spec_changes strict mode
  • report final plans as stale when their linked spec changes after approval
  • refuse implement workflows for stale plans until they are replanned/re-approved

Fixes #49

Tests

  • go test ./... -count=1

Fixes #49

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
@kubestellar-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign nicholasjackson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@clubanderson
clubanderson merged commit 1ee0483 into main Sep 24, 2026
6 of 7 checks passed
@clubanderson
clubanderson deleted the fix-strict-stale-49 branch September 24, 2026 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Define what happens when requirements change mid-workflow (strict mode)

1 participant