You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: