release-openwork

Automating patch release notes generation from Git commits extracts commit history since the last tag to draft coherent release notes. This skill standardizes version bumps and tagging across Git workflows to ensure reproducible patch releases.

Standardizing version bumps and tags for patch releases requires fetching tags and creating a fresh worktree from origin/dev. This skill bumps the relevant files to a new vX.Y.Z version and applies consistent tags across teams.

Managing Git worktrees for patch versioning involves setting up a fresh worktree from origin/dev before bumping versions. This approach isolates the release preparation environment, ensuring reproducible version updates and commit-based notes generation.

Automating patch release workflows requires specifying environment setup and worktree management prerequisites. You need access to your Git repository and the ability to fetch tags and create worktrees from origin/dev to run the automation.

Manual drift causes confusion in software versioning and release notes because inconsistent updates lead to mismatched tags and incoherent documentation. Standardizing the OpenWork patch release workflow ensures reproducible bumps and consistent GitHub releases.