| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
|
cc @nodejs/npm |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
Fast-track has been requested by @RafaelGSS. Please 👍 to approve. |
Sorry, something went wrong.
|
I'm requesting fast-track because I need to include it on v20.0.0 and run the CI/release candidate and so on. |
Sorry, something went wrong.
|
The GitHub UI shows a pending CI, but the CI link shows it as finished. Should I land it manually? @nodejs/build |
Sorry, something went wrong.
Yes, if you are reasonably certain that the GitHub widget is showing bad information and CI is in fact complete and successful, you can always land manually. |
Sorry, something went wrong.
Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com> PR-URL: #47516 Reviewed-By: Stephen Belanger <admin@stephenbelanger.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com> PR-URL: #47516 Reviewed-By: Stephen Belanger <admin@stephenbelanger.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com> PR-URL: #47516 Reviewed-By: Stephen Belanger <admin@stephenbelanger.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com> PR-URL: nodejs#47516 Reviewed-By: Stephen Belanger <admin@stephenbelanger.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
| Back | FazBrowse Home | New Git URL |
test-release-npm is failing on #47381 and it seems related to #43716. However, this asserting seems unnecesary, so rather than adjust it (either on npm side or node.js) sounds reasonable to remove that check.
However, it doesn't mean there's no bug in that change. It seems process.exitCode isn't considered when process.exit() is called with undefined. cc: @daeyeon