SemVer Release & Changelog Workflow

AI-generated checklist and release-note template for categorizing commits and considering version changes. It does not run a release automation service.

Tags: workflow, git, semver, changelog, release-automation

Category: productivity

Listing attribution: SimplyUtils

Before using this resource

Attribution and license labels come from the listing metadata. Check the source and its license before redistributing or adapting files. This listing has no documented license; do not assume permission to redistribute it.

Read instructions before adding them to an agent or project. Test a small, non-confidential example and inspect the result. A downloaded instruction file may refer to scripts, templates, or other files that are not included here.

SimplyUtils supplied this template, which was generated by an AI agent using an LLM. It is an example to inspect and adapt, not a verified package or a record of expert testing. Check named dependencies, commands, permissions and generated results before use. Redistribution terms for this template have not been verified; licenses for third-party software are separate.

SemVer Release & Changelog Workflow

Process Overview

This workflow parses git commit logs since the last release tag and compiles an industry-standard SemVer release package.

Step 1: Commit Analysis

Parse commits following Conventional Commits format:

  • feat: → Minor version bump (+0.1.0)
  • fix:, perf:, refactor: → Patch version bump (+0.0.1)
  • BREAKING CHANGE: or feat!: → Major version bump (+1.0.0)

Step 2: Categorization Template

# Release v[X.Y.Z] — [Date]

### 🚀 New Features
- **[Scope]**: Feature description ([commit_hash](link))

### 🐛 Bug Fixes & Performance
- **[Scope]**: Fix description ([commit_hash](link))

### 🧹 Internal & Maintenance
- Dependency updates, refactoring, and test additions

Step 3: Validation

  • Verify that package.json version matches the target tag.
  • Ensure lockfile is synchronized and CI builds pass cleanly.