release-management

You can automate semantic versioning and changelog generation by running scripts that bump version numbers, generate logs from commit messages, and create GitHub releases. This requires Node.js, pnpm, Git, and GitHub CLI to execute the release operations.

The best way to bump version numbers and create release tags is to checkout a release branch, run pnpm version with the target increment, and use GitHub CLI to create the release. This ensures proper version control and automated tag creation.

Yes, you need GitHub CLI to manage release branches and PRs to main. The release management process requires GitHub CLI along with Node.js, pnpm, and Git to handle tag creation and automate release notes on GitHub.

Automatic changelog generation works by parsing commit messages to compile release notes. The Skill extracts commit history, categorizes changes, and outputs a structured changelog file when creating a new semantic versioning tag.

This release management process is specifically designed to automate semantic versioning, changelog generation, and GitHub release creation for CampusOS, ensuring proper version control and release branch management tailored to that environment.

The semantic versioning script requires pnpm because the release management workflow is built around the pnpm environment. Along with Node.js, Git, and GitHub CLI, pnpm is a necessary dependency to execute the version bumping and release operations correctly.