Some people like to keep release notes in the repo.
To do so generally means a release note update commit for every commit on trunk (aka. 50% git history noise) since dripip is designed for making a canary release for every trunk commit.
Dripip should make that possible though for those that want this tradeoff. They have the following options to be specific:
accept 50% git history noise
don't make canary releases
don't update the release notes on canary releases
I can't think of any other ways to trade things off.
Some people like to keep release notes in the repo.
To do so generally means a release note update commit for every commit on trunk (aka. 50% git history noise) since dripip is designed for making a canary release for every trunk commit.
Dripip should make that possible though for those that want this tradeoff. They have the following options to be specific:
I can't think of any other ways to trade things off.