Module proposal 

Automated proposal analysis and isolated release-branch maintenance.

Modules

analysis 🔒

Version bump analysis. Callers supply what Git observed about each unit and how to find the required bump, so the policy here stays pure.

assets 🔒

Dependency assets built from the worktree of the dependency release to pin their digests.

branch 🔒

Mirrored proposal branch maintenance in a disposable worktree.

groups 🔒

Release units grouped and ordered for one commit each.

metadata 🔒

Ownership marker embedded in the maintained proposal PR body.

Structs

ConfiguredProposal

Inputs for applying and synchronizing a configured release proposal.

ProposalWrite 🔒

Everything needed to write a proposal into a worktree.

Revisions 🔒

Revision-file edits that accompany a proposal.

Synchronized 🔒

The branch after a proposal run and the units it left out.

Enums

ProposalError 🔒

A release proposal cannot be analyzed or synchronized.

ProposalOutcome

What a proposal run did.

Functions

propose

Maintain the release proposal branch and its pull request.

propose_versions 🔒

The versions a proposal sets: explicit requests completed to their groups, then the automatic bumps analysis derives from Git history. The proposal carries the dependency updates of each bumped unit.

sync_mode 🔒

Regenerate on request. Otherwise refresh only what the pull request vouches for.

sync_proposal 🔒

Discover configured units, analyze changes, and synchronize the maintained release branch using the evaluated release policy. expectation comes from the open proposal pull request.

without_unfinished 🔒

Split off the pending units, whose file version waits for publication. The remaining units no longer depend on the removed ones.