🌋 A tool for managing Dart projects with multiple packages. With IntelliJ and Vscode IDE support. Supports automated versioning, changelogs & publishing via Conventional Commits.
If having bug fixes or smaller features which are cherry-picked into a separate "release" branch, the changelog is created accordingly. Then the changelog is cherry-picked into the main branch.
Is there some mechanism to avoid having duplicate entries (when doing a further e.g. major release on main) then, or even let melos fix the existing entries by changing the hash of cherry-picked commits?
Reasoning
Now I have to adapt the changelog manually, to remove duplicate entries / change the hashes.
Is there an existing feature request for this?
Command
melos version --fix-changelog
Description
If having bug fixes or smaller features which are cherry-picked into a separate "release" branch, the changelog is created accordingly. Then the changelog is cherry-picked into the main branch. Is there some mechanism to avoid having duplicate entries (when doing a further e.g. major release on main) then, or even let melos fix the existing entries by changing the hash of cherry-picked commits?
Reasoning
Now I have to adapt the changelog manually, to remove duplicate entries / change the hashes.
Additional context and comments
No response