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

tools: update gyp-next to 0.18.3 #55464

Merged
merged 1 commit into from
Oct 22, 2024
Merged

Conversation

nodejs-github-bot
Copy link
Collaborator

This is an automated update of gyp-next to 0.18.3.

@nodejs-github-bot nodejs-github-bot added gyp Issues and PRs related to the GYP tool and .gyp build files tools Issues and PRs related to the tools directory. labels Oct 20, 2024
@nodejs-github-bot
Copy link
Collaborator Author

Review requested:

  • @nodejs/gyp

@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. needs-ci PRs that need a full CI run. labels Oct 20, 2024
Copy link

codecov bot commented Oct 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.42%. Comparing base (61e52c8) to head (2450f38).
Report is 26 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #55464   +/-   ##
=======================================
  Coverage   88.41%   88.42%           
=======================================
  Files         653      653           
  Lines      187513   187513           
  Branches    36096    36104    +8     
=======================================
+ Hits       165791   165805   +14     
+ Misses      14961    14950   -11     
+ Partials     6761     6758    -3     

see 37 files with indirect coverage changes

@RedYetiDev
Copy link
Member

Does this even need a CI? It's only doc changes on our end.

@legendecas
Copy link
Member

legendecas commented Oct 21, 2024

I think it is not necessary but our tools will complain on it if CI did not run.

@lpinca lpinca added the request-ci Add this label to start a Jenkins CI on a PR. label Oct 22, 2024
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Oct 22, 2024
@nodejs-github-bot
Copy link
Collaborator Author

@richardlau richardlau added the commit-queue Add this label to land a pull request using GitHub Actions. label Oct 22, 2024
@richardlau
Copy link
Member

Does this even need a CI? It's only doc changes on our end.

If anyone is wondering, gyp-next@0.18.3 was not a doc-only update -- it includes the upstream version of #55249 but since that was already applied here it's not showing up in this PR.

@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Oct 22, 2024
@nodejs-github-bot nodejs-github-bot merged commit a3693d2 into main Oct 22, 2024
76 checks passed
@nodejs-github-bot
Copy link
Collaborator Author

Landed in a3693d2

@nodejs-github-bot nodejs-github-bot deleted the actions/tools-update-gyp-next branch October 22, 2024 12:37
aduh95 pushed a commit that referenced this pull request Oct 23, 2024
PR-URL: #55464
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues and PRs related to build files or the CI. gyp Issues and PRs related to the GYP tool and .gyp build files needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants