Module release 

Automated release publishing driven by conventional commits.

The publisher analyzes commits since the last release tag through the GitHub REST API, bumps the Cargo manifest version, and creates the release commit, tag, and GitHub Release without shelling out to git — so it runs in minimal containers. Failures after object creation but before the branch ref update leave only unreachable git objects behind, which GitHub garbage-collects; the window between tag creation and release creation is not auto-healed and requires a manual gh release create for the tag.

Structs

ReleaseOptions

ReleasePublisher

ReleaseReport

Enums

ReleaseAction

What a run does once its analysis finds a version to release, or on a dry run what it would have done. Recorded so a dry run can say which path the real run takes, not just which version it computed.

ReleaseOutcome

ReleasePhase

Which part of the release a run performs.

TagStyle

How the release tag is created. Annotated tags are the default: they carry a tagger identity and satisfy git cat-file -t == "tag" provenance checks. The moving major alias tag is always lightweight.