Skip to content

Handle a toolkit version difference once one is detected #330

Description

@sameera

Decide and build what happens when a stage reads an artifact stamped with a toolkit version different from its own — the warn/waiver/block ladder — together with the optional minimum-version floor beneath it.

Meta

Why it was deferred

The writer stamp (#251) makes a version difference detectable; this stub is the ladder that decides what to do about one. Reaching a difference requires two toolkit versions in play across a single artifact's life. Today exactly one component set exists per user account, one person works these repositories, and no CI workflow invokes a pipeline stage — so the ladder's population is currently empty, while each rung would be a change to a pipeline stage's contract carried forever.

The minimum-version floor is deferred with it and shares the same trigger.

Revisit trigger

A second person working one repository, or a continuous-integration workflow invoking a pipeline stage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogepicEpic (created by nxs-gh-create-epic)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions