Open
Description
Feature request
What is the expected behavior?
To have a single CHANGES.md/CHANGELOG.md file, sync'd with git tags (moving forward)
Even better, to have it curated by hand
What is motivation or use case for adding/changing the behavior?
It's not currently possible for users to understand what's happening in the project without disproportionate effort.
How should this be implemented in your opinion?
- One file.
- Markdown
- Named
CHANGES.mdorCHANGELOG.mdorRELEASES.md - Sync'd with git tags
- New PRs should be required to update change file and describe their change
- Upon releasing, the changes should be written out by hand and curated
Example, assume v5.63.0
## v5.63.0 - 2021-11-09
### Features
- allow passing chunkLoading: false to disable on-demand loading
#### Bugfixes
- fix import 'single-quote' in esm build dependenciesAre you willing to work on this yourself?
I will port it over by hand if maintainers can agree on a style / format ahead of time.