Update CHANGELOG.md and improve /update-changelog command (#795) (#795)

## Summary

This PR corrects the CHANGELOG.md to properly reflect the v9.3.0 release
that was published today, and improves the `/update-changelog` slash
command to prevent future misalignment.

## Changes

### CHANGELOG.md Updates
- Moved three user-visible bug fixes from "Unreleased" section to v9.3.0
section:
  - PR #786: Enhanced error handling for better security and debugging
- PR #778: Improved type safety and error handling in configExporter
module
  - PR #774: Default template no longer triggers production warning
- Updated v9.3.0 release date from October 28 to November 2, 2025
(actual tag date)

### /update-changelog Command Improvements
- Added critical instructions to check version tag dates first
- Added logic to detect when a tag is ahead of the main branch
- Added step to determine where entries should go based on version
boundaries
- Prevents future changelog issues by verifying version dates match
actual tag dates

## Why This Was Needed

The v9.3.0 tag was created today and is actually ahead of the main
branch. The three PRs that were in the "Unreleased" section were
actually part of the v9.3.0 release and needed to be moved to that
version section.

## Test Plan

- [x] Linting passes (\`yarn lint\`)
- [x] All changelog entries properly formatted with correct PR links and
authors
- [x] File ends with newline character
- [x] Release date matches actual tag date

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude <[email protected]>

Author: justin808

.claude/commands/update-changelog.md

@@ -86,32 +86,50 @@ When a new version is released:
 
 ### For Regular Changelog Updates
 
-1. **Check commits since last release**:
-   - Run `git log` to see commits on main/master since the last released version
+1. **Determine the correct version tag to compare against**:
+   - First, check the tag dates: `git log --tags --simplify-by-decoration --pretty="format:%ai %d" | head -10`
+   - Find the latest version tag and its date
+   - Compare main branch date to the tag date
+   - If the tag is NEWER than main, it means main needs to be updated to include the tag's commits
+   - **CRITICAL**: Always use `git log TAG..BRANCH` to find commits that are in the tag but not in the branch, as the tag may be ahead
+
+2. **Check commits and version boundaries**:
+   - Run `git log --oneline LAST_TAG..main` to see commits since the last release
+   - Also check `git log --oneline main..LAST_TAG` to see if the tag is ahead of main
+   - If the tag is ahead, entries in "Unreleased" section may actually belong to that tagged version
    - Identify which commits contain user-visible changes
    - Extract PR numbers and author information from commit messages
    - **Never ask the user for PR details** - get them from the git history
 
-2. **Validate** that changes are user-visible (per the criteria above). If not user-visible, skip those commits.
+3. **Validate** that changes are user-visible (per the criteria above). If not user-visible, skip those commits.
 
-3. **Read the current CHANGELOG.md** to understand the existing structure and formatting.
+4. **Read the current CHANGELOG.md** to understand the existing structure and formatting.
 
-4. **Add entries** to the `## [Unreleased]` section under appropriate category headings.
+5. **Determine where entries should go**:
+   - If the latest version tag is NEWER than main branch, move entries from "Unreleased" to that version section
+   - If main is ahead of the latest tag, add new entries to "Unreleased"
+   - Always verify the version date in CHANGELOG.md matches the actual tag date
 
-5. **Verify formatting**:
+6. **Add or move entries** to the appropriate section under appropriate category headings.
+   - **CRITICAL**: When moving entries from "Unreleased" to a version section, merge them with existing entries under the same category heading
+   - **NEVER create duplicate section headings** (e.g., don't create two "### Fixed" sections)
+   - If the version section already has a category heading (e.g., "### Fixed"), add the moved entries to that existing section
+   - Maintain the category order: Breaking Changes, Added, Changed, Improved, Security, Fixed, Deprecated, Removed
+
+7. **Verify formatting**:
    - Bold description with period
    - Proper PR link
    - Proper author link
    - Consistent with existing entries
    - File ends with a newline character
 
-6. **Run linting** after making changes:
+8. **Run linting** after making changes:
 
    ```bash
    yarn lint
    ```
 
-7. **Show the user** the added entries.
+9. **Show the user** the added or moved entries and explain what was done.
 
 ### For Beta to Non-Beta Version Release
 

CHANGELOG.md

@@ -11,6 +11,8 @@
 
 Changes since the last non-beta release.
 
+## [v9.3.0] - November 2, 2025
+
 ### Fixed
 
 - **Enhanced error handling for better security and debugging**. [PR #786](https://github.com/shakacode/shakapacker/pull/786) by [justin808](https://github.com/justin808).
@@ -29,8 +31,9 @@ Changes since the last non-beta release.
   - Eliminates confusing warning about `useContentHash: false` not being allowed in production
   - Development environment now explicitly sets `useContentHash: false` for faster builds
   - Production no longer needs explicit override since it inherits the correct default
-
-## [v9.3.0] - October 28, 2025
+- Fixed Rails constant error when using custom environments like staging. [PR #681](https://github.com/shakacode/shakapacker/pull/681) by [justin808](https://github.com/justin808). `RAILS_ENV=staging` no longer causes "uninitialized constant Shakapacker::Instance::Rails" error. Shakapacker now works in non-Rails contexts.
+- Fixed TypeScript type definitions to export proper types instead of `any`. [PR #684](https://github.com/shakacode/shakapacker/pull/684) by [justin808](https://github.com/justin808). Previously `package/index.d.ts` was exporting all types as `any`, breaking IDE autocomplete. Now properly exports typed interfaces.
+- Fixed integrity config handling and sass-loader version check. [PR #688](https://github.com/shakacode/shakapacker/pull/688) by [justin808](https://github.com/justin808). Properly handles subresource integrity configuration and correctly detects sass-loader version for conditional logic.
 
 ### Added
 
@@ -62,12 +65,6 @@ Changes since the last non-beta release.
 - **Improved error messages** to suggest `assets_bundler_config_path`. [PR #712](https://github.com/shakacode/shakapacker/pull/712) by [justin808](https://github.com/justin808). More helpful error messages when bundler config is not found, suggesting use of `assets_bundler_config_path` for custom locations.
 - **Improved doctor command output** clarity and accuracy. [PR #682](https://github.com/shakacode/shakapacker/pull/682) by [justin808](https://github.com/justin808). Better formatting and organization of diagnostic information with more actionable recommendations.
 
-### Fixed
-
-- Fixed Rails constant error when using custom environments like staging. [PR #681](https://github.com/shakacode/shakapacker/pull/681) by [justin808](https://github.com/justin808). `RAILS_ENV=staging` no longer causes "uninitialized constant Shakapacker::Instance::Rails" error. Shakapacker now works in non-Rails contexts.
-- Fixed TypeScript type definitions to export proper types instead of `any`. [PR #684](https://github.com/shakacode/shakapacker/pull/684) by [justin808](https://github.com/justin808). Previously `package/index.d.ts` was exporting all types as `any`, breaking IDE autocomplete. Now properly exports typed interfaces.
-- Fixed integrity config handling and sass-loader version check. [PR #688](https://github.com/shakacode/shakapacker/pull/688) by [justin808](https://github.com/justin808). Properly handles subresource integrity configuration and correctly detects sass-loader version for conditional logic.
-
 ## [v9.2.0] - October 9, 2025
 
 ### Added