Add changelog entries for recent releases
See original GitHub issueNone of the GitHub releases have descriptions:
https://github.com/BitGo/BitGoJS/releases
And the last 10 releases have not been documented in RELEASE_NOTES.md
.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Changelog entries - GitLab Docs
Each list item, or entry, in our CHANGELOG.md file is generated from the subject line of a Git commit. Commits are included when...
Read more >Keep a Changelog
There should be an entry for every single version. The same types of changes should be grouped. Versions and sections should be linkable....
Read more >How To Automatically Generate A Helpful Changelog From ...
Creating a changelog is a usual task if a new software version is going to be released. It contains all the changes which...
Read more >A Beginner's Guide to Git — What is a Changelog and How to ...
A changelog is a file that shares a chronologically ordered list of the changes you've made on your project. It's often organized by...
Read more >How to get the changelog entry for last release #786 - GitHub
When standard-version generates new changelog entry, I want to extract this entry and use it to update a gitlab release for that tag...
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
Thanks for the heads up. We typically update the release notes within 48 hours of release, but are a little slower this time around.
I will create a PR to update the release notes for the following versions later today:
4.49.1
,4.49.2
5.0.1
,5.0.2
,5.0.3
,5.0.4
Thanks for the update 😃
The changelog definitely should be versioned, yes. Best practice is to also copy the changelog entries into the GitHub release descriptions:
It gets tiring having to try to hunt down release notes in different places in a lot of repos when updating dependencies, it is always a relief when the GitHub release has all the info.
When people watch the repo for releases, it is a much better experience when the release notification email has details about the release instead of being blank. Here is an example with Next.js: