Automação de Changelog

Padrões e ferramentas para automatizar a geração de changelogs, notas de lançamento e gerenciamento de versões, seguindo padrões da indústria.

Quando Usar Esta Habilidade

• Configurar a geração automatizada de changelog
• Implementar Commits Convencionais (Conventional Commits)
• Criar fluxos de trabalho para notas de lançamento
• Padronizar formatos de mensagens de commit
• Gerar notas de lançamento para GitHub/GitLab
• Gerenciar versionamento semântico

Conceitos Principais

1. Formato Keep a Changelog

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

## Summary

This release introduces dark mode support and improves checkout performance
by 40%. It also includes important security updates.

## Highlights

### 🌙 Dark Mode

Users can now switch to dark mode from settings. The preference is
automatically saved and synced across devices.

### ⚡ Performance

- Checkout flow is 40% faster
- Reduced bundle size by 15%

## Breaking Changes

None in this release.

## Upgrade Guide

No special steps required. Standard deployment process applies.

## Known Issues

- Dark mode may flicker on initial load (fix scheduled for v2.1.1)

## Dependencies Updated

| Package | From    | To      | Reason                   |
| ------- | ------- | ------- | ------------------------ |
| react   | 18.2.0  | 18.3.0  | Performance improvements |
| lodash  | 4.17.20 | 4.17.21 | Security patch           |

Exemplos de Mensagens de Commit

# Feature with scope
feat(auth): add OAuth2 support for Google login

# Bug fix with issue reference
fix(checkout): resolve race condition in payment processing

Closes #123

# Breaking change
feat(api)!: change user endpoint response format

BREAKING CHANGE: The user endpoint now returns `userId` instead of `id`.
Migration guide: Update all API consumers to use the new field name.

# Multiple paragraphs
fix(database): handle connection timeouts gracefully

Previously, connection timeouts would cause the entire request to fail
without retry. This change implements exponential backoff with up to
3 retries before failing.

The timeout threshold has been increased from 5s to 10s based on p99
latency analysis.

Fixes #456
Reviewed-by: @alice

Melhores Práticas

O Que Fazer

• Siga os Commits Convencionais - Habilita a automação
• Escreva mensagens claras - Seu eu futuro agradecerá
• Referencie issues - Vincule commits a tickets
• Use escopos consistentemente - Defina convenções da equipe
• Automatize lançamentos - Reduza erros manuais

O Que Não Fazer

• Não misture alterações - Uma mudança lógica por commit
• Não pule a validação - Use commitlint
• Não edite manualmente - Apenas changelogs gerados
• Não esqueça de breaking changes - Marque com ! ou rodapé
• Não ignore o CI - Valide commits no pipeline