Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: update gyp-next to v0.20.0 #3149

Merged
merged 1 commit into from
Apr 1, 2025
Merged

Conversation

nodejs-github-bot
Copy link
Collaborator

This is an automated update of the gyp-next to https://github.com/nodejs/gyp-next/releases/tag/v0.20.0.

@cclauss cclauss requested a review from Copilot March 29, 2025 06:39
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the gyp-next dependency to version v0.20.0 and incorporates minor refactorings and maintenance changes across the codebase and workflows. Key changes include:

  • Reordering and consolidating import statements for consistency.
  • Standardizing assert statements and minor improvement in error messages.
  • Updating GitHub Actions workflows to use updated actions, build commands, and testing matrices.

Reviewed Changes

Copilot reviewed 47 out of 49 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
gyp/pylib/gyp/easy_xml.py Reordered import statements.
gyp/pylib/gyp/common_test.py Adjusted assert statement style.
gyp/pylib/gyp/common.py Reordered imports and removed redundant code.
gyp/pylib/gyp/init.py Updated import order and introduced walrus operator in ShlexEnv.
gyp/pylib/gyp/MSVSVersion.py Moved the glob import to the top.
gyp/pylib/gyp/MSVSUtil.py Removed an unnecessary blank line.
gyp/pylib/gyp/MSVSUserFile.py Changed import style for easy_xml.
gyp/pylib/gyp/MSVSToolFile.py Changed import style for easy_xml.
gyp/pylib/gyp/MSVSSettings_test.py Changed import style for MSVSSettings.
gyp/pylib/gyp/MSVSProject.py Changed import style for easy_xml.
gyp/gyp_main.py Reordered import statements.
gyp/docs/InputFormatReference.md Added references for library_dirs in the input formats.
gyp/docs/Hacking.md Updated pip installation command.
gyp/CHANGELOG.md Added changelog entries for version v0.20.0.
gyp/.github/workflows/release-please.yml Updated the build command to use pipx.
gyp/.github/workflows/python_tests.yml Updated testing matrices and linting actions.
gyp/.github/workflows/nodejs.yml Adjusted matrix configuration and added a custom Windows runner.
gyp/.github/workflows/node-gyp.yml Adjusted matrix configuration and updated pip installation command.
Files not reviewed (2)
  • gyp/.gitignore: Language not supported
  • gyp/.release-please-manifest.json: Language not supported
Comments suppressed due to low confidence (2)

gyp/.github/workflows/release-please.yml:29

  • Ensure that pipx is available in the environment or add an installation step for pipx before using it to run the build command.
run: pipx run build

gyp/.github/workflows/node-gyp.yml:20

  • Confirm that using 'windows-2025' as the OS runner in the matrix is intentional and that such a runner is available.
os: windows-2025

@cclauss cclauss self-requested a review March 29, 2025 06:45
@lukekarrys
Copy link
Member

@cclauss @legendecas It doesn't look like it to me, but I wanted to confirm that the breaking changes in gyp-next (nodejs/gyp-next#284) would not constitute a breaking change for node-gyp?

@lukekarrys lukekarrys merged commit 80e9c79 into main Apr 1, 2025
46 checks passed
@lukekarrys lukekarrys deleted the actions/update-gyp-next branch April 1, 2025 11:51
@legendecas
Copy link
Member

legendecas commented Apr 1, 2025

It was marked as a breaking change in gyp-next because of existing gyp in the wild potentially rely on the unintended behavior: nodejs/gyp-next#284 (review) and the unindended behavior was only presented in the make generator.

I don't think node-gyp public interface is affected. But this can be a notable change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants