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

[v18.x] deps: upgrade npm to 10.1.0 #49611

Closed
wants to merge 109 commits into from

Conversation

npm-cli-bot
Copy link
Contributor

This PR contains changes from: [email protected] [email protected]


10.0.0

10.0.0 (2023-08-31)

⚠️ BREAKING CHANGES

  • support for node 14 and 16 has been dropped. npm now supports node ^18.17.0 || >=20.5.0
  • npm no longer treats missing scripts as a special case in workspace mode. Use if-present to ignore missing scripts.
  • @npmcli/agent is now used as the agent for network requests
  • the ci-name config has been removed
  • the hard-coded hashAlgorithm value is no longer being passed through flatOptions
  • the unused tmp config has been removed
  • the hard-coded metrics-registry config has been removed.
  • libnpmpublish will no longer attempt a single automatic retry on 409 responses during publish.
  • support for the strict RFC 8909 mode has been removed. this mode was only enabled when the environ NPM_PACKAGE_ARG_8909_STRICT=1 was set.

Bug Fixes

Documentation

Dependencies

10.1.0

10.1.0 (2023-09-08)

Features

Bug Fixes

Documentation

Dependencies

Linkgoron and others added 30 commits September 6, 2023 22:54
The connection interval should close when httpsServer.close is called
similarly to how it gets cleared when httpServer.close is called.

fixes: nodejs#48373
PR-URL: nodejs#48383
Reviewed-By: Moshe Atlow <[email protected]>
Reviewed-By: Paolo Insogna <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
Reviewed-By: Minwoo Jung <[email protected]>
fix: nodejs#46559
OSX will raise both SIGBUS and SIGSEGV when out of bound memory visit,
This commit set sigaction in OSX for two signals to handle this.

PR-URL: nodejs#46561
Fixes: nodejs#46559
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Minwoo Jung <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Signed-off-by: Darshan Sen <[email protected]>
PR-URL: nodejs#48436
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Moshe Atlow <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Signed-off-by: Michael Dawson <[email protected]>

PR-URL: nodejs#48396
Reviewed-By: Rafael Gonzaga <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
Refs: nodejs#48356

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: nodejs#48367
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Chengzhong Wu <[email protected]>
PR-URL: nodejs#48147
Backport-PR-URL: nodejs#49468
Fixes: nodejs#44898
Reviewed-By: Benjamin Gruenbaum <[email protected]>
When piping a paused Readable to a full Writable we didn't
register a drain listener which cause the src to never
resume.

Refs: nodejs#48666
PR-URL: nodejs#48691
Backport-PR-URL: nodejs#49323
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
PR-URL: nodejs#43942
Backport-PR-URL: nodejs#49539
Fixes: nodejs#40110
Reviewed-By: Geoffrey Booth <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Jacob Smith <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
PR-URL: nodejs#44067
Backport-PR-URL: nodejs#49539
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: nodejs#48483
Reviewed-By: Moshe Atlow <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Mestery <[email protected]>
PR-URL: nodejs#48540
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
PR-URL: nodejs#48896
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Jiawen Geng <[email protected]>
PR-URL: nodejs#48514
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
PR-URL: nodejs#48665
Reviewed-By: Luke Karrys <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
PR-URL: nodejs#48838
Reviewed-By: Luke Karrys <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
The OPENSSL_FIPS guard is only needed for versions of OpenSSL earlier
than 3.0.

Removing the guard for OpenSSL 3 fixes `parallel/test-crypto-fips`
when run with a FIPS enabled OpenSSL 3 configuration.

PR-URL: nodejs#48392
Refs: nodejs#48379
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
PR-URL: nodejs#48413
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
This is the certdata.txt[0] from NSS 3.90, released on 2023-04-06.

This is the version of NSS that shipped in Firefox 113 on
2023-05-09.

Certificates added:
- BJCA Global Root CA1
- BJCA Global Root CA2

[0] https://hg.mozilla.org/projects/nss/raw-file/NSS_3_90_RTM/lib/ckfw/builtins/certdata.txt

PR-URL: nodejs#48416
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
...and remove them triagers

Fixes: nodejs#48155
PR-URL: nodejs#48449
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Introduce APIs that allow for the creation of JavaScript strings without
copying the underlying native string into the engine. The APIs fall back
to regular string creation if the engine's external string APIs are
unavailable. In this case, an optional boolean out-parameter indicates
that the string was copied, and the optional finalizer is called if
given.

PR-URL: nodejs#48339
Fixes: nodejs#48198
Reviewed-By: Daeyeon Jeong <[email protected]>
Signed-off-by: Gabriel Schulhof <[email protected]>
PR-URL: nodejs#48451
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
- `@rollup/[email protected]`
- `[email protected]`

PR-URL: nodejs#48417
Reviewed-By: Moshe Atlow <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
PR-URL: nodejs#48387
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Qingyu Deng <[email protected]>
PR-URL: nodejs#48423
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Mestery <[email protected]>
Implement defining properties via V8's
`v8::Object::CreateDataProperty()`, which is faster for data-valued,
writable, configurable, and enumerable properties.

Re: nodejs#45905
Signed-off-by: Gabriel Schulhof <[email protected]>
PR-URL: nodejs#48440
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Chengzhong Wu <[email protected]>
PR-URL: nodejs#48463
Fixes: nodejs#48452
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: LiviaMedeiros <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
toVFile.readSync() is removed in favor of readSync().

PR-URL: nodejs#48485
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Moshe Atlow <[email protected]>
PR-URL: nodejs#48485
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Moshe Atlow <[email protected]>
PR-URL: nodejs#48487
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Moshe Atlow <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
This change is a fix for handling headersTimeout and requestTimeout
that causes unexpected behavior if the HTTP server is started on boot:

 - the connections to the server can be closed immediately
   with the status HTTP 408

This issue usually happens on IoT or embedded devices where
the reference timestamp (returned by uv_hrtime()) is counted since boot
and can be smaller than the headersTimeout or the requestTimeout value.

Additionally added performance improvement to process the list of
connection only if one of the timers should be processed

PR-URL: nodejs#48291
Reviewed-By: Robert Nagy <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Paolo Insogna <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
@nodejs-github-bot nodejs-github-bot added fast-track PRs that do not need to wait for 48 hours to land. needs-ci PRs that need a full CI run. npm Issues and PRs related to the npm client dependency or the npm registry. v18.x Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch. labels Sep 11, 2023
@github-actions
Copy link
Contributor

Fast-track has been requested by @nodejs-github-bot. Please 👍 to approve.

@lukekarrys lukekarrys marked this pull request as draft September 11, 2023 16:34
@lukekarrys lukekarrys added the request-ci Add this label to start a Jenkins CI on a PR. label Sep 11, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Sep 11, 2023
@nodejs-github-bot
Copy link
Collaborator

@lukekarrys
Copy link
Member

Converting to draft to make it clear that this is not intended to merge. Opened to get CI running as early as possible.

Criteria for possibly merge in the future are:

@ruyadorno
Copy link
Member

heads up @lukekarrys you'll need to also include the commit with [email protected] in this PR

@ruyadorno ruyadorno added the release-agenda Issues and PRs to discuss during the meetings of the Release team. label Sep 11, 2023
@ruyadorno ruyadorno changed the title deps: upgrade npm to 10.1.0 [v18.x] deps: upgrade npm to 10.1.0 Sep 11, 2023
@ruyadorno ruyadorno added baking-for-lts PRs that need to wait before landing in a LTS release. and removed fast-track PRs that do not need to wait for 48 hours to land. labels Sep 11, 2023
@lukekarrys
Copy link
Member

@ruyadorno the commit was created automatically by our CI to include both 10.0.0 and 10.1.0, so its not a cherry pick from #49569.

apologies if this makes it more confusing. i can close this and open a new PR with the cherry picked commits that already landed on main from #49569 and #49423.

@ruyadorno
Copy link
Member

oh I see! personally I find that cherry-picking the commits is going to be less confusing 😊

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

I would prefer if this is delayed while we sort out a licensing question.

cc @nodejs/tsc

@ruyadorno
Copy link
Member

Any news on the license front @mcollina ?

@lukekarrys lukekarrys closed this Oct 3, 2023
@lukekarrys
Copy link
Member

@ruyadorno I think I messed up trying to make this PR use the cherry picked commit to backport. We also just released [email protected] so a new PR to main (#50027) has been opened as well as a new PR to v18.x (#50030), so I have closed this PR.

@richardlau richardlau removed the baking-for-lts PRs that need to wait before landing in a LTS release. label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-ci PRs that need a full CI run. npm Issues and PRs related to the npm client dependency or the npm registry. release-agenda Issues and PRs to discuss during the meetings of the Release team. v18.x Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.