Include dependent packages in the proposed version bump
A patch to @fixture/parser requires updating the exact dependency in @fixture/runner. The plan currently includes only parser, leaving runner pinned to the old release.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Dependency graphs · Semantic versioning · Determinism
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.
Acceptance criteria
- The plan includes transitive dependents whose declared ranges no longer accept the proposed version.
- Packages already accepting the new version are not bumped solely because they depend on it.
- Cycles are reported with a readable cycle path and no files are written.
Implementation constraints
- Declare supported workspace range syntax and reject unsupported protocols.
- Use a stable topological order with package-name tie breaking.
Verification to include
- Plan a chain with exact, compatible-range, and dev-only dependencies and compare expected inclusion.
- Feed a dependency cycle and a missing workspace target; both must fail before preparation.
Deliverables
- Dependency-aware planner and graph fixtures
Rollout and recovery
Expose the graph as plan output before enabling its use in file preparation; rollback to read-only inspection.
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.