Semantic Release

Name: Semantic Release
Author: davidcastagnetoa

davidcastagnetoa/skills

5 installs
1 repo stars
Updated March 10, 2026
davidcastagnetoa/skills

Automate semantic versioning, changelog generation, and releases from Conventional Commits with semantic-release, tagging Docker images per release.

About

Uses semantic-release to derive the next semver version from Conventional Commits, generate a changelog, and publish releases in CI. A developer uses it when automating versioning and release tagging on merges to main.

Configure .releaserc.json plugins including exec to tag/push Docker images
Never tag manually; semantic-release is the single source of version truth

Semantic Release by the numbers

5 all-time installs (skills.sh)
Ranked #193 of 248 Release Management skills by installs in the Skillselion catalog
Data as of Jul 8, 2026 (Skillselion catalog sync)

npx skills add https://github.com/davidcastagnetoa/skills --skill semantic_release

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/davidcastagnetoa/skills/semantic_release.svg)](https://skillselion.com/skills/davidcastagnetoa/skills/semantic_release)

Installs	5
repo stars	★ 1
Last updated	March 10, 2026
Repository	davidcastagnetoa/skills ↗

What it does

Automate semantic versioning, changelog generation, and releases from Conventional Commits with semantic-release, tagging Docker images per release.

Files

SKILL.mdMarkdownGitHub ↗

semantic_release

semantic-release lee los mensajes de commit en formato Conventional Commits y determina automáticamente la próxima versión semántica (major.minor.patch), genera el CHANGELOG y publica el release.

When to use

Usar para versionar el sistema KYC y las imágenes Docker. Cada merge a main que pase CI genera un nuevo release automáticamente.

Instructions

1. Instalar: npm install --save-dev semantic-release @semantic-release/changelog @semantic-release/git 2. Configurar .releaserc.json:

   {
     "branches": ["main"],
     "plugins": [
       "@semantic-release/commit-analyzer",
       "@semantic-release/release-notes-generator",
       "@semantic-release/changelog",
       ["@semantic-release/exec", {
         "publishCmd": "docker tag kyc-api kyc-api:${nextRelease.version} && docker push kyc-api:${nextRelease.version}"
       }],
       "@semantic-release/git"
     ]
   }

3. Convenciones de commit (ver skill conventional_commits): feat: → minor, fix: → patch, feat!: → major. 4. Ejecutar en CI tras merge a main: npx semantic-release. 5. El tag de la versión en Git permite hacer helm upgrade kyc --set image.tag=v1.2.3 con versión específica.

Notes

Nunca tagear versiones manualmente — dejar que semantic-release sea la única fuente de verdad.
La versión 0.x.y indica que la API puede tener breaking changes — pasar a 1.0.0 al estabilizar el contrato.