fix(release): add conventional commits to semantic-release - #656
Merged
Conversation
Configure semantic-release with conventionalcommits preset to fix empty release notes. Added commit-msg hook to enforce format.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
maxtechera
added a commit
that referenced
this pull request
Nov 3, 2025
## Release Summary This release includes critical fixes to the release automation system, establishing conventional commit validation. **Note:** This is the first release using the new conventional commit format with automated validation via commitlint. ## Changes Included ### Bug Fixes - **fix(release)**: Add conventional commits to semantic-release (#656) - Implemented commitlint with conventional commit validation - Added pre-commit hook for commit message linting - Updated semantic-release config to generate proper release notes - Ensures all future commits follow conventional format ## Release Details - **Source Branch**: staging - **Target Branch**: production - **Release Date**: 2025.11.03 - **Semantic Release**: Will auto-generate version based on conventional commits ## Testing - Commitlint validation tested and working - Pre-commit hooks validated - Semantic-release configuration verified ## Deployment Notes - No database migrations required - No manual steps needed - Semantic-release will automatically create GitHub release with notes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
GitHub releases were being created but had empty release notes (e.g., v1.7.2).
Root Cause:
Release: Staging to Production - DATEformatSolution
Configure semantic-release to use conventional commits format and enforce it via git hooks.
Changes
1.
.releaserc.json- semantic-release Configurationconventionalcommitspreset for proper commit parsingchore(release)commits to trigger patch releases2.
.claude/agents/git-pr-manager.md- Enhanced Agentchore(release): staging to production - YYYY.MM.DD3.
.husky/commit-msg- Git Hook (NEW)Commit Format
Going forward, all commits must follow:
Examples:
feat(chat): add file upload support→ Minor releasefix(api): resolve race condition→ Patch releasechore(release): staging to production - 2025.11.03→ Patch release with full notesTesting
✅ Validated commit-msg hook accepts valid conventional commits
✅ Validated commit-msg hook rejects invalid formats
✅ Tested release commit format:
chore(release): ...Impact
Related
Fixes the issue identified in PR #655 where release v1.7.2 had empty notes.