What about CHANGELOG.md

[vovs03]

:question: What about :memo: CHANGELOG.md

If is it possible, it will be cool!

• [ ] CHANGELOG.md

# CHANGELOG

**v.2.3.5**
- `on Sep 30, 2019 `
  - describe

...

**v. 2.3.0**
- `on Jun 26, 2017`
  - describe

[stheine]

especially, if you do major version updates, like the recent 2.x to 3.x, I'd like to understand if there are breaking changes, so a CHANGELOG would be the natural place to search.

[niftylettuce]

@bnoordhuis I recommend to use npm i -g [email protected] and np to publish versions, which will auto-open GitHub releases page (similar to release) and provide a changelog for each version, then you wouldn't need a CHANGELOG and your existing releases would have much more detail

[bnoordhuis]

@niftylettuce I might start using that from now on, thanks for the tip.

@stheine Really the only change is that using iconv from worker_threads now works (#211) and that required bumping the minimum supported node.js version.

[dr-dimitru]

GitHub's releases is the great alternative to CHANGELOG file. But it would be great to read why major change happened, like here:

@bnoordhuis ...required bumping the minimum supported node.js version.

What minimum required node.js version now?

[niftylettuce]

@dr-dimitru see the engines field in package.json https://github.com/bnoordhuis/node-iconv/blob/master/package.json#L15