Package the CLI so a fresh checkout can rehearse a release offline
The maintainer can run the tool only through a source-tree import. Package the command and document one complete rehearsal using fixture packages and the local registry.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Packaging · Developer experience · Release engineering
Estimated field mix
- Developer tooling100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
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.
Setup prerequisites
- Create a temporary Git repository with three related fixture packages.
- Use a local registry double; no publishing credentials are required.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CLI-101 · Print package versions without depending on the current directory
- CLI-103 · Include dependent packages in the proposed version bump
- CLI-104 · Make a dirty checkout a deliberate release decision
- CLI-105 · Turn change fragments into package-specific release notes
- CLI-106 · Prepare manifests and notes as one recoverable file operation
- CLI-107 · Prevent a second release process from using the same checkout
- CLI-108 · Resume a publish rehearsal after the registry response disappears
- CLI-102 · Give scripts a stable JSON output contract
- CLI-109 · Keep release credentials and package contents out of logs
Acceptance criteria
- The built executable supports --help and --version without source imports.
- An offline rehearsal covers inspect, plan, prepare, interrupted publish, and resume.
- The guide explains which steps mutate files and how to restore the fixture repository.
Implementation constraints
- Pin fixture inputs so example output is reproducible.
- Do not perform an actual registry publication.
Verification to include
- Install the packed artifact into a temporary directory and run the documented rehearsal.
- Run without a registry configuration and confirm publishing fails before any network attempt.
Deliverables
- Packed CLI artifact instructions and end-to-end rehearsal guide
Rollout and recovery
Distribute a prerelease artifact for local evaluation; retract it if packed-command behavior differs from source execution.
Value of the work
For the engineer: Practice CLI contracts, graph reasoning, filesystem safety, and recovery from partial work.
For the team: Review how an engineer makes release changes inspectable and recoverable before they affect consumers.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.