Skip to content
This repository was archived by the owner on Aug 27, 2024. It is now read-only.

Update node Docker tag to v20 - #240

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-20.x
Open

Update node Docker tag to v20#240
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-20.x

Conversation

@renovate

@renovate renovate Bot commented Apr 21, 2023 •
edited
Loading

Copy link
Copy Markdown
Contributor

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node stage major 18.11.0-alpine -> 20.17.0-alpine age adoption passing confidence
@types/node (source) dependencies major 16.18.55 -> 20.16.1 age adoption passing confidence

Release Notes

nodejs/node (node)

v20.17.0

Compare Source

v20.16.0: 2024-07-24, Version 20.16.0 'Iron' (LTS), @​marco-ippolito

Compare Source

process: add process.getBuiltinModule(id)

process.getBuiltinModule(id) provides a way to load built-in modules
in a globally available function. ES Modules that need to support
other environments can use it to conditionally load a Node.js built-in
when it is run in Node.js, without having to deal with the resolution
error that can be thrown by import in a non-Node.js environment or
having to use dynamic import() which either turns the module into
an asynchronous module, or turns a synchronous API into an asynchronous one.

if (globalThis.process?.getBuiltinModule) {
  // Run in Node.js, use the Node.js fs module.
  const fs = globalThis.process.getBuiltinModule('fs');
  // If `require()` is needed to load user-modules, use createRequire()
  const module = globalThis.process.getBuiltinModule('module');
  const require = module.createRequire(import.meta.url);
  const foo = require('foo');
}

If id specifies a built-in module available in the current Node.js process,
process.getBuiltinModule(id) method returns the corresponding built-in
module. If id does not correspond to any built-in module, undefined
is returned.

process.getBuiltinModule(id) accepts built-in module IDs that are recognized
by module.isBuiltin(id).

The references returned by process.getBuiltinModule(id) always point to
the built-in module corresponding to id even if users modify
require.cache so that require(id) returns something else.

Contributed by Joyee Cheung in #​52762

doc: doc-only deprecate OpenSSL engine-based APIs

OpenSSL 3 deprecated support for custom engines with a recommendation to switch to its new provider model.
The clientCertEngine option for https.request(), tls.createSecureContext(), and tls.createServer(); the privateKeyEngine and privateKeyIdentifier for tls.createSecureContext(); and crypto.setEngine() all depend on this functionality from OpenSSL.

Contributed by Richard Lau in #​53329

inspector: fix disable async hooks on Debugger.setAsyncCallStackDepth

Debugger.setAsyncCallStackDepth was previously calling the enable function by mistake. As a result, when profiling using Chrome DevTools, the async hooks won't be turned off properly after receiving Debugger.setAsyncCallStackDepth with depth 0.

Contributed by Joyee Cheung in #​53473

Other Notable Changes
  • [09e2191432] - (SEMVER-MINOR) buffer: add .bytes() method to Blob (Matthew Aitken) #​53221
  • [394e00f41c] - (SEMVER-MINOR) doc: add context.assert docs (Colin Ihrig) #​53169
  • [a8601efa5e] - (SEMVER-MINOR) doc: improve explanation about built-in modules (Joyee Cheung) #​52762
  • [5e76c258f7] - doc: add StefanStojanovic to collaborators (StefanStojanovic) #​53118
  • [5e694026f1] - doc: add Marco Ippolito to TSC (Rafael Gonzaga) #​53008
  • [f3ba1eb72f] - (SEMVER-MINOR) net: add new net.server.listen tracing channel (Paolo Insogna) #​53136
  • [2bcce3255b] - (SEMVER-MINOR) src,permission: --allow-wasi & prevent WASI exec (Rafael Gonzaga) #​53124
  • [a03a4c7bdd] - (SEMVER-MINOR) test_runner: add context.fullName (Colin Ihrig) #​53169
  • [69b828f5a5] - (SEMVER-MINOR) util: support --no- for argument with boolean type for parseArgs (Zhenwei Jin) #​53107
Commits

v20.15.1: 2024-07-08, Version 20.15.1 'Iron' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes
Commits

v20.15.0: 2024-06-20, Version 20.15.0 'Iron' (LTS), @​marco-ippolito

Compare Source

test_runner: support test plans

It is now possible to count the number of assertions and subtests that are expected to run within a test. If the number of assertions and subtests that run does not match the expected count, the test will fail.

test('top level test', (t) => {
  t.plan(2);
  t.assert.ok('some relevant assertion here');
  t.subtest('subtest', () => {});
});

Contributed by Colin Ihrig in #​52860

inspector: introduce the --inspect-wait flag

This release introduces the --inspect-wait flag, which allows debugger to wait for attachement. This flag is useful when you want to debug the code from the beginning. Unlike --inspect-brk, which breaks on the first line, this flag waits for debugger to be connected and then runs the code as soon as a session is established.

Contributed by Kohei Ueno in #​52734

zlib: expose zlib.crc32()

This release exposes the crc32() function from zlib to user-land.

It computes a 32-bit Cyclic Redundancy Check checksum of data. If
value is specified, it is used as the starting value of the checksum,
otherwise, 0 is used as the starting value.

The CRC algorithm is designed to compute checksums and to detect error
in data transmission. It's not suitable for cryptographic authentication.

const zlib = require('node:zlib');
const { Buffer } = require('node:buffer');

let crc = zlib.crc32('hello');  // 907060870
crc = zlib.crc32('world', crc);  // 4192936109

crc = zlib.crc32(Buffer.from('hello', 'utf16le'));  // 1427272415
crc = zlib.crc32(Buffer.from('world', 'utf16le'), crc);  // 4150509955

Contributed by Joyee Cheung in #​52692

cli: allow running wasm in limited vmem with --disable-wasm-trap-handler

By default, Node.js enables trap-handler-based WebAssembly bound
checks. As a result, V8 does not need to insert inline bound checks
int the code compiled from WebAssembly which may speedup WebAssembly
execution significantly, but this optimization requires allocating
a big virtual memory cage (currently 10GB). If the Node.js process
does not have access to a large enough virtual memory address space
due to system configurations or hardware limitations, users won't
be able to run any WebAssembly that involves allocation in this
virtual memory cage and will see an out-of-memory error.

$ ulimit -v 5000000
$ node -p "new WebAssembly.Memory({ initial: 10, maximum: 100 });"
[eval]:1
new WebAssembly.Memory({ initial: 10, maximum: 100 });
^

RangeError: WebAssembly.Memory(): could not allocate memory
    at [eval]:1:1
    at runScriptInThisContext (node:internal/vm:209:10)
    at node:internal/process/execution:118:14
    at [eval]-wrapper:6:24
    at runScript (node:internal/process/execution:101:62)
    at evalScript (node:internal/process/execution:136:3)
    at node:internal/main/eval_string:49:3

--disable-wasm-trap-handler disables this optimization so that
users can at least run WebAssembly (with a less optimial performance)
when the virtual memory address space available to their Node.js
process is lower than what the V8 WebAssembly memory cage needs.

Contributed by Joyee Cheung in #​52766

Other Notable Changes
Commits

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/node-20.x branch from a1dc08f to 8cb6e4c Compare May 4, 2023 21:12
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from 8cb6e4c to 03c6a39 Compare May 16, 2023 22:35
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from 03c6a39 to db37b47 Compare June 10, 2023 01:29
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from db37b47 to 9ed7215 Compare June 21, 2023 19:22
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from 9ed7215 to b88398c Compare July 10, 2023 22:10
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from b88398c to e34a21c Compare July 21, 2023 22:45
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from e34a21c to 00d6809 Compare August 10, 2023 20:20
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 2 times, most recently from 7f86243 to 6088cb1 Compare September 11, 2023 18:15
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from 6088cb1 to c4b0165 Compare September 20, 2023 01:03
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from c4b0165 to 25c8a56 Compare September 29, 2023 19:25
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from 25c8a56 to 27f9205 Compare October 16, 2023 20:11
@renovate renovate Bot changed the title Update Node.js to v20 Update Node.js to v20 - autoclosed Oct 20, 2023
@renovate renovate Bot closed this Oct 20, 2023
@renovate
renovate Bot deleted the renovate/node-20.x branch October 20, 2023 01:23
@renovate renovate Bot changed the title Update Node.js to v20 - autoclosed Update Node.js to v20 Oct 24, 2023
@renovate renovate Bot reopened this Oct 24, 2023
@renovate
renovate Bot restored the renovate/node-20.x branch October 24, 2023 00:20
@renovate renovate Bot changed the title Update Node.js to v20 Update dependency @types/node to v20 Oct 24, 2023
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 2 times, most recently from 64ed480 to d018199 Compare October 25, 2023 18:59
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from d018199 to a1fdd39 Compare October 31, 2023 11:23
@renovate
renovate Bot force-pushed the renovate/node-20.x branch from a1fdd39 to eaf5b11 Compare November 7, 2023 22:36
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 4 times, most recently from 9d4a6f1 to ecc9e98 Compare November 22, 2023 04:03
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 3 times, most recently from f6f448a to 4560038 Compare November 29, 2023 21:11
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 5 times, most recently from b9bdc33 to 3b9605a Compare January 17, 2024 08:44
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 7 times, most recently from 6197d60 to e018da4 Compare January 31, 2024 01:41
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 3 times, most recently from e1b68b2 to e9121e3 Compare February 1, 2024 19:04
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 3 times, most recently from 1859e5e to 0148940 Compare February 15, 2024 17:01
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 2 times, most recently from 4aa7944 to 4d92974 Compare February 22, 2024 19:44
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 4 times, most recently from 5dcbd96 to 04b3ce1 Compare February 29, 2024 18:17
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 3 times, most recently from a7f359a to a4b35a3 Compare March 13, 2024 14:03
@renovate
renovate Bot force-pushed the renovate/node-20.x branch 2 times, most recently from bc4c6ad to e490df0 Compare March 18, 2024 23:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants