changelog-maintenance

Organize and document software releases with semantic versioning and standardized changelog formats. CHANGELOG.md : Version number : MAJOR.MINOR.PATCH Examples : #changelog #release-notes #versioning #semantic-versioning #documentation - Provides Keep a Changelog format with seven standard categories (Added, Changed, Deprecated, Removed, Fixed, Security, Unreleased) for consistent release documentation - Enforces semantic versioning rules (MAJOR.MINOR.PATCH) with clear guidance on when to increment each version component - Includes templates for user-facing release notes, migration guides for breaking changes, and API deprecation workflows - Requires reverse-chronological ordering, ISO 8601 dates, and specific language to avoid vague entries like "bug fixes" - Before release : organize changes before shipping a version - Continuous : update whenever significant changes occur - Migration guide : document breaking changes - 1.0.0 → 1.0.1 : bug fix - 1.0.1 → 1.1.0 : new feature - 1.1.0 → 2.0.0 : Breaking change - Reverse chronological : latest version at the top - Include dates : ISO 8601 format (YYYY-MM-DD) - Categorize entries : Added, Changed, Fixed, etc. - No copying Git logs : write from the user's perspective - Vague wording : "Bug fixes", "Performance improvements" (be specific) - Keep a Changelog : follow the standard format - Semantic Versioning : consistent version...