v0.5.5 release prep #348
v0.5.5 release prep #348
Conversation
CHANGELOG.md
Outdated
| @@ -2,6 +2,17 @@ | |||
|
|
|||
| ## Unreleased | |||
There was a problem hiding this comment.
Have we not been removing this between releases? Should we?
There was a problem hiding this comment.
We could remove it since we don't use it, but I also wish we used it...
There was a problem hiding this comment.
I'll try out using it for the next release cycle and see how it goes. If we don't like it we'll remove it.
It's nice to keep a log of the changes as we make them so that we don't miss anything important when it comes to releasing. Also makes it easier on the person piloting the release 😄
There was a problem hiding this comment.
We could remove it since we don't use it, but I also wish we used it...
How hard would it be to write two scripts:
- Adds ##Unreleased to CHANGELOG at the same time the package.json is bumped
- Add the commit message as a bullet point under ##Unreleased after each merge
There was a problem hiding this comment.
Adds ##Unreleased to CHANGELOG at the same time the package.json is bumped
Add the commit message as a bullet point under ##Unreleased after each merge
Both are possible and can be easily accomplished using existing tools. There's even one built and maintained by Microsoft called beachball
There are also simpler ones, like the one used by the SWA CLI repository which generates the changelog based on prefixes you add to the commit message
No description provided.