Skip to content

A put-but-never-frozen WorkTask manifest cannot be replaced #1069

Description

@realproject7

pipelineStore.retire and the retire_batch Head action now let a frozen batch retire so a successor manifest can be frozen for the same project. That path only covers the frozen stage.

A manifest that was written with put_batch_manifest but never frozen leaves the domain in the manifest stage with no retirement path, so it can neither be replaced nor advanced. Head has to be able to abandon a manifest it decided against.

Noted while wiring batch retirement; deliberately left out of that change to keep its scope reviewable.

Parent: #1028.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions