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
I was just writing up the v4 release notes and it occurred to me that we could automate the version bumping of addons (#2410) when a stable version changed. We could do this by identifying the changed files between the previous release tag (latest on npm) and HEAD, instead of just the commit that we do here:
Then if files changed within the addon, do a new stable release. In order to keep to semver's breaking changes we could just assume any change to an addon is a breaking change with a previous version and bump major here.
The text was updated successfully, but these errors were encountered:
I was just writing up the v4 release notes and it occurred to me that we could automate the version bumping of addons (#2410) when a stable version changed. We could do this by identifying the changed files between the previous release tag (
latest
on npm) andHEAD
, instead of just the commit that we do here:xterm.js/bin/publish.js
Lines 111 to 117 in 26a09f0
Then if files changed within the addon, do a new stable release. In order to keep to semver's breaking changes we could just assume any change to an addon is a breaking change with a previous version and bump major here.
The text was updated successfully, but these errors were encountered: