should we ditch the changelog tooling?
See original GitHub issueI spent over 2hrs trying to cut a release today.
- no one is using
npm run c
- @dbouwman says it can fail sometimes, possibly due to the issue where
[Unreleased]
ends up underneath the latest release? - this sucks
- it becomes the job of whomever is cutting the release to manually come up w/ CHANGELOG entries that look like the generated ones
I’m over it.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Should you use a changelog tool? - Canny Blog
1. It keeps all updates in one place · 2. Close the feedback loop on feature requests · 3. It's the perfect place...
Read more >Keep a Changelog
Keep an Unreleased section at the top to track upcoming changes. This serves two purposes: People can see what changes they might expect...
Read more >List of Top Changelog Tools 2022 - TrustRadius
Changelog Tools reviews, comparisons, alternatives and pricing. The best Changelog solutions for small business to enterprises.
Read more >Changelog and Release Notes Software for Product Updates ...
Changelogs are software solutions that offer a platform to craft and publish your changelogs, eliminating the need to add the release notes manually....
Read more >What Makes a Good Changelog - WorkOS
Changelogs are important communication tools, and should be made for people to enjoy reading. Here are five decisions we made to make the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Idea/Goal: can we switch to automatic releases through semantic release? We would need to make sure it works with monorepos.
Fair.
npm run c
was only failing for me because of the Husky version. Since I bumped it, the problem was solved ¯_(ツ)_/¯