[v14.x] deps: upgrade npm to 6.14.17 #42900
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The sks-keyservers.net is no longer listed by DNS PR-URL: nodejs#39227 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
If `ccache` is available, use it during V8 builds on ppc64le and s390x. Only create the `gcc` and `g++` shims if necessary. PR-URL: nodejs#42204 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Fixes: nodejs#42296 PR-URL: nodejs#42357 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
PR-URL: nodejs#42736 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
Original commit message:
[runtime] Change default scope info for SyntheticFunctionContexts
This changes the default scope info for SyntheticFunctionContexts
to the EmptyScopeInfo which does not contain an extension slot.
The bug happened because, previously, the native context scope info
was used as dummy.
Change-Id: I4d6bf6918c11c79201d16bde99ed76800ad6f6c5
Bug: v8:10629
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2277806
Commit-Queue: Victor Gomes <victorgomes@chromium.org>
Commit-Queue: Leszek Swirski <leszeks@chromium.org>
Auto-Submit: Victor Gomes <victorgomes@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/master@{#68636}
Refs: v8/v8@367b0c1
PR-URL: nodejs#42637
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Original commit message:
fix overflow check in error formatting
Bug: v8:12494
Change-Id: Iba2684173296aa236f1a1c73a5606c21472eff06
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3426634
Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
Commit-Queue: Gus Caplan <snek@chromium.org>
Cr-Commit-Position: refs/heads/main@{#78909}
Refs: v8/v8@cc9a8a3
PR-URL: nodejs#41826
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Danielle Adams <adamzdanielle@gmail.com>
nodejs-github-bot
added
dont-land-on-v12.x
fast-track
|
Fast-track has been requested by @nodejs-github-bot. Please 👍 to approve. |
aduh95
changed the title
Merged
github-actions
bot
removed
the
request-ci
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Mesteery
approved these changes
Apr 28, 2022
VoltrexKeyva
approved these changes
Apr 29, 2022
This comment was marked as outdated.
This comment was marked as outdated.
lpinca
approved these changes
Apr 29, 2022
27 tasks
29 tasks
juanarbol
pushed a commit
that referenced
this pull request
May 1, 2022
PR-URL: #42900 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Mestery <mestery@protonmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol
added a commit
that referenced
this pull request
May 1, 2022
Notable Changes doc: * New release key for Bryan English Learn more at: #42102 Contributed by Bryan English (@bengl) npm: * Upgrade `npm` to `v16.14.17`. Learn more at: #42900 Contributed by Ruy Adorno (@ruyadorno) V8: * V8 had a stack overflow issue affecting the `vm` module, cherry-picking `cc9a8a37445e` (941b023) from V8 solves this issue. Learn more at: #41826 Contributed by @devsnek * Using `getHeapSnapshot()` was causing a Node.js crash due a V8 issue, this is fixed by backporting `367b0c1e7a32` (v8/v8@367b0c1) from V8. Learn more at: #42637 Contributed by Chengzhong Wu (@legendecas)
juanarbol
added a commit
that referenced
this pull request
May 1, 2022
Notable Changes doc: * New release key for Bryan English Learn more at: #42102 Contributed by Bryan English (@bengl) npm: * Upgrade `npm` to `v16.14.17`. Learn more at: #42900 Contributed by Ruy Adorno (@ruyadorno) V8: * V8 had a stack overflow issue affecting the `vm` module, cherry-picking `cc9a8a37445e` (941b023) from V8 solves this issue. Learn more at: #41826 Contributed by @devsnek * Using `getHeapSnapshot()` was causing a Node.js crash due a V8 issue, this is fixed by backporting `367b0c1e7a32` (v8/v8@367b0c1) from V8. Learn more at: #42637 Contributed by Chengzhong Wu (@legendecas)
30 tasks
juanarbol
added a commit
that referenced
this pull request
May 2, 2022
Notable Changes doc: * New release key for Bryan English Learn more at: #42102 Contributed by Bryan English (@bengl) npm: * Upgrade `npm` to `v6.14.17`. Learn more at: #42900 Contributed by Ruy Adorno (@ruyadorno) V8: * V8 had a stack overflow issue affecting the `vm` module, cherry-picking `cc9a8a37445e` (941b023) from V8 solves this issue. Learn more at: #41826 Contributed by @devsnek * Using `getHeapSnapshot()` was causing a Node.js crash due a V8 issue, this is fixed by backporting `367b0c1e7a32` (v8/v8@367b0c1) from V8. Learn more at: #42637 Contributed by Chengzhong Wu (@legendecas)
|
Landed in a3ebdbf |
33 tasks
juanarbol
added a commit
that referenced
this pull request
May 3, 2022
Notable Changes doc: * New release key for Bryan English Learn more at: #42102 Contributed by Bryan English (@bengl) npm: * Upgrade `npm` to `v6.14.17`. Learn more at: #42900 Contributed by Ruy Adorno (@ruyadorno) V8: * V8 had a stack overflow issue affecting the `vm` module, cherry-picking `cc9a8a37445e` (v8/v8@cc9a8a3) from V8 solves this issue. Learn more at: #41826 Contributed by @devsnek * Using `getHeapSnapshot()` was causing a Node.js crash due a V8 issue, this is fixed by backporting `367b0c1e7a32` (v8/v8@367b0c1) from V8. Learn more at: #42637 Contributed by Chengzhong Wu (@legendecas) PR-URL: #42899
juanarbol
added a commit
that referenced
this pull request
May 3, 2022
Notable Changes doc: * New release key for Bryan English Learn more at: #42102 Contributed by Bryan English (@bengl) npm: * Upgrade `npm` to `v6.14.17`. Learn more at: #42900 Contributed by Ruy Adorno (@ruyadorno) V8: * V8 had a stack overflow issue affecting the `vm` module, cherry-picking `cc9a8a37445e` (v8/v8@cc9a8a3) from V8 solves this issue. Learn more at: #41826 Contributed by Gus Caplan (@devsnek) * Using `getHeapSnapshot()` was causing a Node.js crash due a V8 issue, this is fixed by backporting `367b0c1e7a32` (v8/v8@367b0c1) from V8. Learn more at: #42637 Contributed by Chengzhong Wu (@legendecas) PR-URL: #42899
juanarbol
added a commit
that referenced
this pull request
May 3, 2022
Notable Changes doc: * New release key for Bryan English Learn more at: #42102 Contributed by Bryan English (bengl) npm: * Upgrade `npm` to `v6.14.17`. Learn more at: #42900 Contributed by Ruy Adorno (ruyadorno) V8: * V8 had a stack overflow issue affecting the `vm` module, cherry-picking `cc9a8a37445e` (v8/v8@cc9a8a3) from V8 solves this issue. Learn more at: #41826 Contributed by Gus Caplan (devsnek) * Using `getHeapSnapshot()` was causing a Node.js crash due a V8 issue, this is fixed by backporting `367b0c1e7a32` (v8/v8@367b0c1) from V8. Learn more at: #42637 Contributed by Chengzhong Wu (legendecas) PR-URL: #42899
34 tasks
juanarbol
added a commit
that referenced
this pull request
May 4, 2022
Notable Changes doc: * New release key for Bryan English Learn more at: #42102 Contributed by Bryan English (bengl) npm: * Upgrade `npm` to `v6.14.17`. Learn more at: #42900 Contributed by Ruy Adorno (ruyadorno) V8: * V8 had a stack overflow issue affecting the `vm` module, cherry-picking `cc9a8a37445e` (v8/v8@cc9a8a3) from V8 solves this issue. Learn more at: #41826 Contributed by Gus Caplan (devsnek) * Using `getHeapSnapshot()` was causing a Node.js crash due a V8 issue, this is fixed by backporting `367b0c1e7a32` (v8/v8@367b0c1) from V8. Learn more at: #42637 Contributed by Chengzhong Wu (legendecas) PR-URL: #42899
juanarbol
added a commit
that referenced
this pull request
May 4, 2022
Notable Changes doc: * New release key for Bryan English Learn more at: #42102 Contributed by Bryan English (bengl) npm: * Upgrade `npm` to `v6.14.17`. Learn more at: #42900 Contributed by Ruy Adorno (ruyadorno) V8: * V8 had a stack overflow issue affecting the `vm` module, cherry-picking `cc9a8a37445e` (v8/v8@cc9a8a3) from V8 solves this issue. Learn more at: #41826 Contributed by Gus Caplan (devsnek) * Using `getHeapSnapshot()` was causing a Node.js crash due a V8 issue, this is fixed by backporting `367b0c1e7a32` (v8/v8@367b0c1) from V8. Learn more at: #42637 Contributed by Chengzhong Wu (legendecas) PR-URL: #42899
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
6.14.17 (2022-04-28)
DEPENDENCIES
a869ec48bansi-regex@4.1.1a869ec48bminimist@1.2.6