Your MCP FacturaScripts project is now configured for fully automated releases using semantic-release and GitHub Actions.
- GitHub Actions workflow (
.github/workflows/release.yml) - Semantic Release configuration (
.releaserc.json) - Conventional commit guidelines (
.github/COMMIT_CONVENTION.md) - Complete setup guide (
.github/SEMANTIC_RELEASE_SETUP.md)
- Bug report template (
.github/ISSUE_TEMPLATE/bug_report.md) - Feature request template (
.github/ISSUE_TEMPLATE/feature_request.md) - Pull request template (
.github/pull_request_template.md)
- Semantic release dependencies installed
- Repository URLs configured (needs your GitHub URL)
- New npm scripts added for release management
Edit package.json and replace placeholder with your actual GitHub repository URL:
{
"repository": {
"type": "git",
"url": "https://github.com/YOUR_USERNAME/mcp-facturascripts.git"
}
}git add .
git commit -m "feat: setup automated semantic release and GitHub templates"
git push origin mainThe commit above will trigger your first automated release creating version 1.1.0!
| Commit Type | Version Change | Example |
|---|---|---|
fix: |
Patch (1.0.2 β 1.0.3) | fix: handle API timeout errors |
feat: |
Minor (1.0.2 β 1.1.0) | feat: add new analytics tool |
feat!: |
Major (1.0.2 β 2.0.0) | feat!: change API response format |
- β Analyzes your commit messages
- β Determines next version number
- β Updates package.json version
- β Generates changelog from commits
- β Creates Git tag (e.g., v1.1.0)
- β Publishes GitHub release with notes
- β Uploads build artifacts
- β
Push to
mainbranch with semantic commits - β Manual trigger via GitHub Actions UI
- β No release if only
docs:,chore:,style:commits
Test locally without creating actual releases:
# Dry run to see what would happen
npm run semantic-release:dry
# Check commit analysis
npx semantic-release --dry-run- Setup Guide:
.github/SEMANTIC_RELEASE_SETUP.md - Commit Guide:
.github/COMMIT_CONVENTION.md - Project Changelog:
CHANGELOG.md(auto-updated)
Your project now has enterprise-grade release automation:
- π Continuous Integration with automated testing
- π Standardized commits with conventional format
- π Automated releases with proper versioning
- π Auto-generated changelogs from commits
- π·οΈ Git tags and GitHub releases
- π Release artifacts automatically uploaded
- π Issue templates for better project management
- π¬ PR templates for consistent contributions
Next commit to main will create your first automated release! π―