Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before building the app, please back up your
streamlink-twitch-gui{,-test}
config folder(s), so that you're able to downgrade later on again if you need to.Checklist
This is caused by an improperly implemented workaround in Chromium (https://crbug.com/804637) which made it into this NW.js release. Has been fixed just recently and will land in NW.js hopefully soon.
nw-builder
sometimes fails while downloading the new NW.js release archivesDidn't happen again, must have been an issue with the servers.
Minor breaking changes
start.sh
wrapper script on Linux.If you're running Streamlink Twitch GUI from the Linux tarballs, you'll have to run
remove-menuitems.sh
once before upgrading and runadd-menuitems.sh
after upgrading for setting up a new menu shortcut. This change is not tied to the NW.js upgrade, but was overdue a long time ago. The available Linux packages won't be affected on the next release, as they include properly packaged menu shortcuts.Why is Github still showing the wrong commit order after my forced branch pushes? Not that it matters, but...