Release notes created incorrectly
See original GitHub issueHello, is it normal that my releases lack proper formatting even though I’m correctly using Conventional Commit messages? See here please: https://github.com/coformatique/prisma-auth0-starter/releases
I’m using conventional-github-releaser -p angular
as can be seen in my package.json file.
Thank you
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Incorrect logic in release note creation · Issue #282 - GitHub
Hi,. I have used gren for both creating changelog file and generating release notes on the GH releases and have the same wrong...
Read more >How to write release notes (+5 great examples) | Appcues Blog
How to write release notes · 1. Make the intent of the changes clear · 2. Focus release notes on the user ·...
Read more >How to Write Release Notes Your Users Will Actually Read
Do product release notes matter? Yes. Here's how to follow best practices for your release notes and ensure they actually get read.
Read more >Short updates are boring. Release notes new format. How to ...
A release note is a report informing readers of the new version of a product, or an update, or a bug fix. Such...
Read more >Part One Release Notes Issues and Best Practices - YouTube
Part One looks at the challenges involved in creating release notes and best practices for delivering high-quality releases:Why release ...
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
In a different project I faced this issue again. Looks like the cli version is not working correctly.
A simple node script works fine:
github-release.js
call with
node github-release.js
.@hbetts I had the same issue.
npm i --save-dev conventional-changelog-angular
did the trick for me. thx!