Changelog-Driven Releases

1. alkymi

   1 5 44 8.0 Python

   Pythonic task automation

   

   I also use a similar approach for my open source Python automation project, alkymi: https://github.com/MathiasStokholm/alkymi/blob/develop/CHANG...

   In addition to the author's comments, I would suggest also using the format from https://keepachangelog.com/en/1.1.0/ (more sub-headings, e.g. "added").

   Lastly, pruning the CHANGELOG upon adding and removing stuff again is a great idea to keep entries meaningful for the reader.

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. epage

   2 2 - -

   My problem with maintaining a changelog during development is it can serve as a source of merge conflicts. Instead, I follow Covnentional Commit style and manually write my changelog entries based on the commits. I have a tool [0] that can show me the relevant commits for a package in my repo and automates the entire release process, including doing sanity checks.

   I also feel like releasing from CI is hard, especially if you have multiple packages in a repo [1], including

   - You can't as easily introspect the process

   - You can't as easily recover from failure

   - Getting a lot of the nuance right, like handling releases concurrent to merging of PRs, is difficult

   - When the workflow is an ever-present "release PR" that you merge when ready has issues with selecting which packages to release and at what version

   I have been considering making a tool to generate changelogs from fragments. Been keeping notes at https://github.com/epage/epage.github.io/issues/23

   [0]: https://github.com/crate-ci/cargo-release

   [1]: https://github.com/MarcoIeni/release-plz/discussions/1019

4. cargo-release

   3 11 1,371 9.0 Rust

   Cargo subcommand `release`: everything about releasing a rust crate.

   

   My problem with maintaining a changelog during development is it can serve as a source of merge conflicts. Instead, I follow Covnentional Commit style and manually write my changelog entries based on the commits. I have a tool [0] that can show me the relevant commits for a package in my repo and automates the entire release process, including doing sanity checks.

   I also feel like releasing from CI is hard, especially if you have multiple packages in a repo [1], including

   - You can't as easily introspect the process

   - You can't as easily recover from failure

   - Getting a lot of the nuance right, like handling releases concurrent to merging of PRs, is difficult

   - When the workflow is an ever-present "release PR" that you merge when ready has issues with selecting which packages to release and at what version

   I have been considering making a tool to generate changelogs from fragments. Been keeping notes at https://github.com/epage/epage.github.io/issues/23

   [0]: https://github.com/crate-ci/cargo-release

   [1]: https://github.com/MarcoIeni/release-plz/discussions/1019

5. release-plz

   4 6 908 9.7 Rust

   Publish Rust crates from CI with a Release PR.

   

   My problem with maintaining a changelog during development is it can serve as a source of merge conflicts. Instead, I follow Covnentional Commit style and manually write my changelog entries based on the commits. I have a tool [0] that can show me the relevant commits for a package in my repo and automates the entire release process, including doing sanity checks.

   I also feel like releasing from CI is hard, especially if you have multiple packages in a repo [1], including

   - You can't as easily introspect the process

   - You can't as easily recover from failure

   - Getting a lot of the nuance right, like handling releases concurrent to merging of PRs, is difficult

   - When the workflow is an ever-present "release PR" that you merge when ready has issues with selecting which packages to release and at what version

   I have been considering making a tool to generate changelogs from fragments. Been keeping notes at https://github.com/epage/epage.github.io/issues/23

   [0]: https://github.com/crate-ci/cargo-release

   [1]: https://github.com/MarcoIeni/release-plz/discussions/1019

6. towncrier

   5 5 807 8.9 Python

   Manage the release notes for your project.

   

   I don't really like writing the change log automatically from commits. I think those both have a slightly different audience and thus need different wording.

   I know the frustration of merge conflicts on the change log file.

   Right now, I'm creating change logs by hand which is time consuming to do on release time. I'm considering switching to using towncrier or something similar, where you have a changes dir with one file per change for creating change logs --> https://towncrier.readthedocs.io/

Suggest a related project