-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Comparing changes
Open a pull request
base repository: nodejs/node-gyp
base: v12.1.0
head repository: nodejs/node-gyp
compare: v12.2.0
- 15 commits
- 26 files changed
- 12 contributors
Commits on Nov 18, 2025
-
Fix typos in some files (#3245)
Co-authored-by: khanhkhanhlele <[email protected]>
Edge-Seven and khanhkhanhlele authoredNov 18, 2025 2Configuration menu - View commit details
-
Copy full SHA for 858bb26 - Browse repository at this point
Copy the full SHA 858bb26View commit details
Commits on Nov 21, 2025
-
build(deps): bump actions/checkout from 5 to 6 (#3248)
Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v5...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for db5385c - Browse repository at this point
Copy the full SHA db5385cView commit details
Commits on Dec 19, 2025
-
feat: include built package version in error logs (#3254)
I'm working on upgrading a lot of packages to node 24 and there are many failures in native modules. Looking at logs alone it's hard to spot which package versions are failing to build. node-gyp prints debug info about node, npm, and node-gyp but not the package that is currently being built. It doesn't look like node-gyp reads package.json so I opted to read npm_package_ env vars, which is similar to the npm_config_ env vars node-gyp already reads.
Configuration menu - View commit details
-
Copy full SHA for ee9cbdd - Browse repository at this point
Copy the full SHA ee9cbddView commit details
Commits on Dec 30, 2025
-
msvs_version is no longer a valid npm config setting (#3257)
Remove misleading warnings. % `npm config list -l | grep msvs` % `npm config set msvs_version=2025` > npm error `msvs_version` is not a valid npm option
Configuration menu - View commit details
-
Copy full SHA for 6c2e374 - Browse repository at this point
Copy the full SHA 6c2e374View commit details
Commits on Jan 2, 2026
-
fix: cpu concurrency detection on some platforms (#3255)
`os.availableParallelism()` should produce more accurate results of how much parallelism should be used then `os.cpus().length`. The only breaking change is the newer API requires node versions >= v18.x which is fine as node-gyp only aims to support latest and LTS releases. And the oldest LTS release still supported as of this commit is v22. Fixes #3191
Configuration menu - View commit details
-
Copy full SHA for f15b79a - Browse repository at this point
Copy the full SHA f15b79aView commit details -
fix: python is no longer a valid npm config setting (#3258)
Remove misleading warnings. % `npm config list -l | grep python ` # no hits % `npm config set python=3.14` > npm error `python` is not a valid npm option <!-- Thank you for your pull request. Please review the below requirements. Contributor guide: https://github.com/nodejs/node/blob/main/CONTRIBUTING.md --> ##### Checklist <!-- Remove items that do not apply. For completed items, change [ ] to [x]. --> - [ ] `npm install && npm run lint && npm test` passes - [ ] tests are included <!-- Bug fixes and new features should include tests --> - [ ] documentation is changed or added - [x] commit message follows [commit guidelines](https://github.com/googleapis/release-please#how-should-i-write-my-commits) ##### Description of change <!-- Provide a description of the change -->
Configuration menu - View commit details
-
Copy full SHA for c7c678f - Browse repository at this point
Copy the full SHA c7c678fView commit details
Commits on Jan 4, 2026
-
Configuration menu - View commit details
-
Copy full SHA for a52bc81 - Browse repository at this point
Copy the full SHA a52bc81View commit details -
2
Configuration menu - View commit details
-
Copy full SHA for 7b4f315 - Browse repository at this point
Copy the full SHA 7b4f315View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3f81949 - Browse repository at this point
Copy the full SHA 3f81949View commit details
Commits on Jan 16, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 0407877 - Browse repository at this point
Copy the full SHA 0407877View commit details
Commits on Jan 17, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 0f2bc7d - Browse repository at this point
Copy the full SHA 0f2bc7dView commit details
Commits on Jan 19, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 30cda26 - Browse repository at this point
Copy the full SHA 30cda26View commit details
Commits on Jan 26, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 888ff2c - Browse repository at this point
Copy the full SHA 888ff2cView commit details -
chore(deps): upgrade tar to 7.5.4 to address CVE-2026-23950 (#3271)
Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: cclauss <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 7bf371c - Browse repository at this point
Copy the full SHA 7bf371cView commit details
Commits on Jan 27, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 878061f - Browse repository at this point
Copy the full SHA 878061fView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v12.1.0...v12.2.0