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

[Snyk] Upgrade node-gyp from 9.4.0 to 9.4.1 #364

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

revagomes
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade node-gyp from 9.4.0 to 9.4.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released a month ago, on 2023-10-27.
Release notes
Package name: node-gyp
  • 9.4.1 - 2023-10-27

    Bug Fixes

    • Revert "update make-fetch-happen to 11.0.3 (#2796)" (82c2d64)

    Tests

    Miscellaneous

    • add release branches as ci targets (b68da05)
    • add release-please to v9 branch (5a65d03)
    • increase parallel install timeouts (fd77b34)
  • 9.4.0 - 2023-06-13

    Features

    • add support for native windows arm64 build tools (bb76021)
    • Upgrade Python linting from flake8 to ruff (#2815) (fc0ddc6)

    Bug Fixes

    • extract tarball to temp directory on Windows (#2846) (aaa117c)
    • log statement is for devDir not nodedir (#2840) (55048f8)

    Miscellaneous

    • get update-gyp.py to work with Python >= v3.5 (#2826) (337e8e6)

    Doc

    Tests

from node-gyp GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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.

2 participants