Add the automated addition of the new version to the CHANGELOG.md file #124
Replies: 3 comments 3 replies
-
Automating the whole release workflow is doable, but complex. I managed to do it for my projects by relying on GitHub reused workflows. All my code is available here at: https://github.com/kdeldycke/workflows There are a lot of moving parts and this is tailored to my preferences and needs. Took me basically 2 years to have something fully automated. |
Beta Was this translation helpful? Give feedback.
-
@coordt is also maintaining a |
Beta Was this translation helpful? Give feedback.
-
@ScottWilliamAnderson @kdeldycke I have thought about documenting the automation of this project. It generates a version hint as part of PRs, does GitHub releases, CHANGELOGs, etc. And boy, let me tell you, debugging an automation pipeline sucks! But this one is pretty dialed in. What other steps would be necessary? |
Beta Was this translation helpful? Give feedback.
-
bump-my-version is brilliant for automating new versions. We use it for 100% of our new versions across all our internal packages! But we're struggling to find an easy way to automatically add the version and (ideally) the short description of the release into the CHANGELOG.md file of each repository that we use it in.
What do you think of having bump-my-version include a way to automatically append the new release, and perhaps add a way to describe the changes in the newest version?
Ah, as a final note, we don't use Github for hosting the repository, so we can't make use of Github's release notes functionality unfortunately.
Thanks! Looking forward to hear what you think
Beta Was this translation helpful? Give feedback.
All reactions