Skip to content

About

Understand how NW.js changes upstream behaviour

Resources

Code of conduct

Stars

3 stars

Watchers

1 watching

Forks

Latest commit

 

History

72 Commits

Folders and files

Repository files navigation

NW.js Patches

Understand how NW.js changes upstream behaviour.

Versions

  • NW: 0.120.0
  • Chromium: 157.0.8103.39
  • Node: 26.12.1
  • V8: 15.7.112.23

Patching process

.github/patch clones NW.js's forks of Chromium, Node.js and V8 (at the nw-v<version> tag if there is one, otherwise main), downloads the matching upstream release sources, and writes the difference to patches/<project>.patch with git diff --no-index. Files added by NW.js are included in full and files it removes are listed without their contents. The script fails without writing patches if either tree's version does not match the pinned version, for example when NW.js's main has already moved past or not yet reached a release.

The release workflow runs on every push to main, daily at 00:00 UTC, and manually via workflow_dispatch. It:

  1. Checks https://nwjs.io/versions.json for a new NW.js release and reads its Chromium and Node.js versions.
  2. Reads the V8 version from https://github.com/nwjs/v8/blob/main/include/v8-version.h.
  3. If the versions in .github/patch are not the latest, updates them and the Versions header above (see .github/bump), regenerates the patches, and opens a pull request on the patches/nw-<version> branch.

The patch workflow runs on every pull request to main. It regenerates the patches from the versions in .github/patch and commits them to the pull request branch if they changed. Pull requests opened by the release workflow do not trigger it, so that workflow generates the patches itself.

About

Understand how NW.js changes upstream behaviour

Resources

Code of conduct

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors