This repository uses a streamlined approach to automatic versioning, changelog generation, and releases based on conventional commits.

• Triggers: Push to main branch
• Purpose: Automatic versioning and release management
• Features:
  • Calculates next version from conventional commits
  • Updates package.json automatically
  • Generates high-quality changelog
  • Creates git tags and GitHub releases
  • Uses Changesets for professional package management

• Triggers: PR opened, edited, or new commits
• Purpose: Ensures commit messages follow conventional format
• Features:
  • Validates all commits in PR
  • Comments with validation results
  • Provides fix instructions for invalid commits
  • Updates comment automatically on new commits

• Triggers: New git tags created
• Purpose: Runs development and production builds
• Features:
  • Development build runs automatically
  • Production build requires manual approval
  • Environment-based approval workflow

Use conventional commit format for automatic versioning:

# Feature (minor version bump)
git commit -m "feat: add user authentication"

# Bug fix (patch version bump)  
git commit -m "fix: resolve login issue"

# Breaking change (major version bump)
git commit -m "feat!: redesign API

BREAKING CHANGE: API endpoints have changed"

# Maintenance (patch version bump)
git commit -m "chore: update dependencies"

1. Create PR with conventional commits
2. PR validation automatically checks commit format
3. Fix any invalid commits if needed
4. Merge PR to main
5. Release workflow automatically:
   • Calculates next version
   • Updates package.json
   • Generates changelog
   • Creates tag and GitHub release

• GITHUB_TOKEN (automatically provided)
• NPM_TOKEN (if publishing to npm)

• Create production environment in GitHub for manual approval
• Configure reviewers for production builds

• package.json - Version automatically updated
• CHANGELOG.md - Persistent changelog maintained
• Git tags - New version tags created
• GitHub Releases - Releases with changelog created

✅ Zero developer overhead - just write conventional commits
✅ Automatic versioning - no manual version management
✅ Professional changelogs - high-quality changelog generation
✅ PR validation - ensures commit format compliance
✅ Build automation - development and production builds
✅ Manual approval - production builds require approval

• Check if commit message contains [skip ci]
• Ensure you're pushing to main branch
• Check Actions tab for any errors

• Verify commit messages follow conventional format
• Check if commits are actually new since last tag
• Look at workflow logs for semver calculation details

• Update commit messages to follow conventional format
• Use interactive rebase to fix commit messages
• Force push after changes

• Conventional Commits
• Changesets
• Semantic Versioning