Module dependent_version_plan 

The dependent-version plan with exact manifest bytes before and after. What: Plan patch bumps for publishable dependents of packages whose version differs from the base, with the exact manifest bytes before and after each bump. Why: This is the one planner behind both entry points: the commit-time policy and the release workflow’s ripple, which will call the native wrapper’s direct fix. It is the incumbent’s planWorkspaceBumps (dependent-bump-workflow.ts:280-388) over the content seam: it starts no Git process and reads no file.

In TS you’d write (pseudocode):

// const plan = await planWorkspaceBumps(reader);

Structs

ManifestBump

What: One dependent bump with the manifest change that performs it. Vec<u8> holds exact file bytes. Why: The policy turns it into a full-content patch of a tracked file; the release path writes replacement after checking the file still holds original.

WorkspaceBumpPlan

What: A completed plan. Why: The finding message names the raised packages; the bumps are sorted by name.

Enums

PlanOutcome

What: How planning ended when nothing failed. Why: A dependent that needs a bump but holds no plain release stops the plan; the policy reports it for a bump by hand, the release path fails.

Functions

plan_workspace_bumps

What: Plan patch bumps for publishable dependents of raised packages. Why: Reads every manifest at both states; the registry configuration only when a version was raised; source files only of dependents whose development edges could carry a raised version.