You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The NPM packages currently ship without a changelog. It should be relatively easy to create one automatically though, with some diff-ing logic (starting point exists in build-diff.js).
At a minimum, the changelog could link to the corresponding pre-release pull request, which includes the diff from the previous version.
It should be possible to amend the changelog manually, e.g. to override the automatically generated message in situations where we add a new property or change a setting that affects a large number of entries.
The text was updated successfully, but these errors were encountered:
The NPM packages currently ship without a changelog. It should be relatively easy to create one automatically though, with some diff-ing logic (starting point exists in
build-diff.js
).At a minimum, the changelog could link to the corresponding pre-release pull request, which includes the diff from the previous version.
It should be possible to amend the changelog manually, e.g. to override the automatically generated message in situations where we add a new property or change a setting that affects a large number of entries.
The text was updated successfully, but these errors were encountered: