chore: prepare release v2.1.2

Author: sQVe

CHANGELOG.md

@@ -7,12 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [2.1.2] - 2025-07-30
-
-### Fixed
-
-- Preserve trailing delimiters instead of moving to beginning. This resolves an issue where trailing delimiters (like commas at the end of lists) were incorrectly repositioned to the start of sorted content.
-
 ### Added
 
 - Enhanced release script with automation support. The release script now supports CI environments, dry-run mode, and improved validation for streamlined releases.
@@ -22,6 +16,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Enhanced error handling and validation across core modules for improved stability.
 - Updated test infrastructure to use minimal_init.lua for better test isolation and reliability.
 
+## [2.1.2] - 2025-07-30
+
+### Fixed
+
+- Preserve trailing delimiters instead of moving to beginning. This resolves an issue where trailing delimiters (like commas at the end of lists) were incorrectly repositioned to the start of sorted content.
+
 ## [2.1.1] - 2025-07-12
 
 ### Fixed

RELEASE.md

@@ -14,8 +14,9 @@ This document outlines the automated process for creating a new release of sort.
    ```
 
 The script automatically handles:
+
 - Version validation and conflict checking
-- Test execution and code formatting verification  
+- Test execution and code formatting verification
 - Version updates in `lua/sort/init.lua`
 - Git commit, tagging, and pushing to origin
 
@@ -29,17 +30,70 @@ The script automatically handles:
 ## Post-release
 
 After the tag is pushed, GitHub Actions will:
+
 - Run the full test suite
 - Create a GitHub release with changelog notes
 - Generate downloadable archives
 
 ## Version Numbering
 
 This project follows [Semantic Versioning](https://semver.org/):
+
 - **MAJOR**: Incompatible API changes
-- **MINOR**: New functionality in a backwards compatible manner  
+- **MINOR**: New functionality in a backwards compatible manner
 - **PATCH**: Backwards compatible bug fixes
 
+## Changelog Validation
+
+GitHub Actions enforces strict semantic versioning rules for changelog validation. Understanding these rules prevents release failures:
+
+### Semantic Versioning Rules
+
+**Patch releases (x.y.Z)** - Only backward-compatible bug fixes:
+
+- ✅ **Allowed sections**: `Fixed`, `Security`
+- ❌ **Not allowed**: `Added`, `Changed`, `Deprecated`, `Removed`
+
+**Minor releases (x.Y.z)** - New functionality, backward-compatible:
+
+- ✅ **Allowed sections**: `Added`, `Changed`, `Fixed`, `Security`, `Deprecated`
+- ❌ **Not allowed**: `Removed` (unless it's deprecated functionality)
+
+**Major releases (X.y.z)** - Breaking changes:
+
+- ✅ **Allowed sections**: All sections including `Removed`
+
+### Common Validation Errors
+
+**Error**: `Only 'fixed, security' sections are allowed for version x.y.Z`
+
+- **Cause**: Patch release contains `Added` or `Changed` sections
+- **Solution**: Either:
+  1. Move `Added`/`Changed` items to `Unreleased` section and create patch release
+  2. Delete tag and create minor release (x.Y+1.0) instead
+
+**Error**: Changelog entry validation failed
+
+- **Cause**: Version section missing or malformed in CHANGELOG.md
+- **Solution**: Ensure proper format: `## [x.y.z] - YYYY-MM-DD`
+
+### Version Selection Guide
+
+Choose version type based on your changes:
+
+- **Bug fixes only** → Patch release (2.1.2)
+- **New features or enhancements** → Minor release (2.2.0)
+- **Breaking changes** → Major release (3.0.0)
+
 ## Troubleshooting
 
-If the release script fails, it provides clear error messages and suggestions. For GitHub Actions issues, check the workflow logs at: https://github.com/sQVe/sort.nvim/actions
+If the release script fails, it provides clear error messages and suggestions. For GitHub Actions issues, check the workflow logs at: https://github.com/sQVe/sort.nvim/actions
+
+### Release Workflow Failures
+
+If GitHub Actions release fails after tagging:
+
+1. Check the workflow logs for specific error messages
+2. Fix the issue (often changelog validation)
+3. Amend the relevant commits and force-push to re-trigger the workflow
+4. If needed, delete and recreate the tag with corrected content

lua/sort/init.lua

@@ -5,7 +5,7 @@ local utils = require('sort.utils')
 local mappings = require('sort.mappings')
 
 local M = {
-  _VERSION = '2.1.1',
+  _VERSION = '2.1.2',
   _DESCRIPTION = 'Sorting plugin for Neovim',
   _URL = 'https://github.com/sQVe/sort.nvim',
   _LICENSE = 'MIT',