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

fix: bump @mapbox/node-pre-gyp #462

Merged
merged 1 commit into from
Jan 27, 2025
Merged

Conversation

talentlessguy
Copy link
Contributor

@mapbox/node-pre-gyp just released their version 2 a few days ago, this pull request simply bumps rc to stable v2

@talentlessguy talentlessguy requested review from ijjk, styfle and a team as code owners January 26, 2025 23:43
Copy link

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@mapbox/node-pre-gyp@2.0.0 🔁 npm/@mapbox/node-pre-gyp@2.0.0-rc.0 Transitive: network, shell +46 6.11 MB mapbox-admin, mapbox-machine-user, mapbox-npm, ...25 more

View full report↗︎

Copy link
Contributor

@EndangeredMassa EndangeredMassa left a comment

Choose a reason for hiding this comment

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

It looks like there's no real change between these versions.

node-pre-gyp does say it doesn't support Node 16, which we still need to do, but the RC we're currently using already said that. So, I think this is a fine change.

Thanks!

@styfle styfle changed the title chore: bump @mapbox/node-pre-gyp fix: bump @mapbox/node-pre-gyp Jan 27, 2025
@styfle styfle enabled auto-merge (squash) January 27, 2025 18:26
@styfle styfle merged commit 0e6e120 into vercel:main Jan 27, 2025
13 checks passed
@talentlessguy talentlessguy deleted the bump-node-pre-gyp branch January 27, 2025 19:11
Copy link

🎉 This PR is included in version 0.29.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

3 participants