Open jimsynz opened 7 months ago
I wonder how we could detect this...while semantic versions have meaning between each other, they don't necessarily have an explicit "step" between versions enforce. i.e the next version after 2.1.0-charmander
could be 2.2.0-charizard
. We could apply a heuristic and warn on common patterns though?
We could just make sure that the tag is present for the version we find in the mix file before we apply any changes.
oh, right, duh. That is much simpler!
I recently did a release of Ash that generated a change log with a heap of extra stuff in it. I'm guessing that it's because I didn't have the previous version's tag fetched locally so the diff was incorrectly generated.
This should probably be detected and the command aborted with an error.