Loading noCV…
Preparing the next view without exposing private workflow data.
Preparing the next view without exposing private workflow data.
A team maintains six related packages. Release notes, version changes, and tags are copied between a spreadsheet and a terminal; a failed upload recently left two packages ahead of their dependents. The exercise uses temporary repositories and a fake registry.
Practice brief · Version 5Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
Practice CLI contracts, graph reasoning, filesystem safety, and recovery from partial work.
Review how an engineer makes release changes inspectable and recoverable before they affect consumers.
A release-plan CLI, local fixtures, recovery tests, and an operator guide.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Produce a deterministic release plan from repository inputs.
Write only the planned files and make failure recovery explicit.
Resume against a fake registry without duplicating or concealing work.
Produce a deterministic release plan from repository inputs.
Estimated field mix
Estimated field mix
Estimated field mix
Write only the planned files and make failure recovery explicit.
Estimated field mix
Estimated field mix
Estimated field mix
Resume against a fake registry without duplicating or concealing work.
Estimated field mix
Estimated field mix
Estimated field mix
Estimated field mix
CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.