fantasia-changelog-en-us

Automated release notes generation reads the package.json version and existing changeLog.md headings to synchronize the English in-app changelog with the current project version, applying semver patch bumps automatically as needed.

To keep your English changelog in sync, the tool reads package.json.version and updates the top section of src/i18n/en-US/documents/changeLog.md, preserving existing history while aligning the heading with the current version.

You should update your in-app changelog after any substantive app changes, UX updates, test modifications, or documentation updates to ensure the release notes accurately reflect the new project version.

Yes, the tool optionally consults local planning context in .cursor/plans to surface relevant release notes and structure, generating context-aware changelog entries while preserving the existing markdown history.

When the latest changelog heading duplicates the package version, semantic versioning rules apply a patch bump automatically, incrementing the version number and generating a new section for the release notes.