feat: Author and activate YAML workflow versions #324

Closed
opened 2026-07-13 19:46:14 +02:00 by dries · 0 comments
Owner

Parent

#311

What to build

Allow users to import, validate, publish, export, compare, and activate human-readable YAML workflow versions while preserving one canonical execution representation shared with JSON.

Acceptance criteria

  • YAML and JSON representations normalize to the same canonical validated definition.
  • Parsing rejects duplicate keys, unsupported values, and ambiguous coercions with source-oriented errors.
  • Publishing creates an immutable monotonically identifiable version.
  • Users can inspect version history, compare versions, and select the active version for future manual/triggered runs.
  • Existing runs remain pinned when a newer version is activated.
  • Subworkflow versions are resolved and pinned before run execution.
  • The production editor shows validation errors and the read-only graph from the same parsed definition.
  • Exported YAML is stable enough for source control review.
  • Tests cover equivalent YAML/JSON, parser edge cases, activation races, and run pinning.

Blocked by

## Parent #311 ## What to build Allow users to import, validate, publish, export, compare, and activate human-readable YAML workflow versions while preserving one canonical execution representation shared with JSON. ## Acceptance criteria - [ ] YAML and JSON representations normalize to the same canonical validated definition. - [ ] Parsing rejects duplicate keys, unsupported values, and ambiguous coercions with source-oriented errors. - [ ] Publishing creates an immutable monotonically identifiable version. - [ ] Users can inspect version history, compare versions, and select the active version for future manual/triggered runs. - [ ] Existing runs remain pinned when a newer version is activated. - [ ] Subworkflow versions are resolved and pinned before run execution. - [ ] The production editor shows validation errors and the read-only graph from the same parsed definition. - [ ] Exported YAML is stable enough for source control review. - [ ] Tests cover equivalent YAML/JSON, parser edge cases, activation races, and run pinning. ## Blocked by - #313
dries closed this issue 2026-07-16 00:56:10 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dries/ocman#324
No description provided.