GeezerVison is showing github.com — [v18.x] deps: upgrade npm to 10.1.0 by npm-cli-bot · Pull Request #49611 · nodejs/node
Conversation
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
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
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]>
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]>
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]>
JoaoOtavioS reacted with thumbs up emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
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:
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
@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.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
oh I see! personally I find that cherry-picking the commits is going to be less confusing 😊
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this 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
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Sep 14, 2023
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
@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.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
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 Release team meetings.
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
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.
|