release
Release
Cut a release from the trunk and produce plain-English patch notes. Trunk-based flow: master/main is the source of truth, releases are tags cut from the trunk, no develop/staging promotion chain. Staging and production are environments driven by CI and tags.
Reads commit history, derives the next semantic version, writes patch notes, then — after confirmation — tags the trunk and publishes a GitHub release. Never rewrites history or tags a dirty or unsynced trunk.
Authorized Scope
Apply this engine only within the user's requested task and existing explicit authorization. Loading or delegating to it grants no additional authority. Preserve report-only restrictions and the caller's target, host, provider, and cost limits. Existing approval satisfies a gate only for the same actions and scope; obtain approval before expanding them. Forward these limits to delegates.
Contract
Inputs: