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

Update Docker (major)#147

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-docker
Open

Update Docker (major)#147
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-docker

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Oct 27, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
node final major 10.16.0 -> 20.15.0
postgres final major 11.14 -> 16.3

Release Notes

nodejs/node (node)

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

v20.14.0: 2024-05-28, Version 20.14.0 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

v20.13.1: 2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Compare Source

2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Revert "tools: install npm PowerShell scripts on Windows"

Due to a regression in the npm installation on Windows, this commit reverts the change that installed npm PowerShell scripts on Windows.

Commits
  • [b7d80802cc] - Revert "tools: install npm PowerShell scripts on Windows" (marco-ippolito) #​52897

v20.13.0: 2024-05-07, Version 20.13.0 'Iron' (LTS), @​marco-ippolito

Compare Source

2024-05-07, Version 20.13.0 'Iron' (LTS), @​marco-ippolito

buffer: improve base64 and base64url performance

The performance of the base64 and base64url encoding and decoding functions has been improved significantly.

Contributed by Yagiz Nizipli in #​52428

crypto: deprecate implicitly shortened GCM tags

This release, introduces a doc-only deprecation of using GCM authentication tags that are shorter than the cipher's block size, unless the user specified the authTagLength option.

Contributed by Tobias Nießen in #​52345

events,doc: mark CustomEvent as stable

From this release CustomEvent has been marked stable.

Contributed by Daeyeon Jeong in #​52618

fs: add stacktrace to fs/promises

Sync functions in fs throwed an error with a stacktrace which is helpful for debugging. But functions in fs/promises throwed an error without a stacktrace. This commit adds stacktraces by calling Error.captureStacktrace and re-throwing the error.

Contributed by 翠 / green in #​49849

report: add --report-exclude-network option

New option --report-exclude-network, also available as report.excludeNetwork, enables the user to exclude networking interfaces in their diagnostic report. On some systems, this can cause the report to take minutes to generate so this option can be used to optimize that.

Contributed by Ethan Arrowood in #​51645

src: add uv_get_available_memory to report and process

From this release it is possible to get the available memory in the system by calling process.getAvailableMemory().

Contributed by theanarkh #​52023

stream: support typed arrays

This commit adds support for typed arrays in streams.

Contributed by IlyasShabi #​51866

util: support array of formats in util.styleText

It is now possible to pass an array of format strings to util.styleText to apply multiple formats to the same text.

console.log(util.styleText(['underline', 'italic'], 'My italic underlined message'));

Contributed by Marco Ippolito in #​52040

v8: implement v8.queryObjects() for memory leak regression testing

This is similar to the queryObjects() console API provided by the Chromium DevTools console. It can be used to search for objects that have the matching constructor on its prototype chain in the heap after a full garbage collection, which can be useful for memory leak regression tests.
To avoid surprising results, users should avoid using this API on constructors whose implementation they don't control, or on constructors that can be invoked by other parties in the application.

To avoid accidental leaks, this API does not return raw references to the objects found. By default, it returns the count of the objects found. If options.format is 'summary', it returns an array containing brief string representations for each object. The visibility provided in this API is similar to what the heap snapshot provides, while users can save the cost of serialization and parsing and directly filer the target objects during the search.

We have been using this API internally for the test suite, which has been more stable than any other leak regression testing strategies in the CI. With a public implementation we can now use the public API instead.

const { queryObjects } = require('node:v8');
class A { foo = 'bar'; }
console.log(queryObjects(A)); // 0
let a = new A();
console.log(queryObjects(A)); // 1
// [ "A { foo: 'bar' }" ]
console.log(queryObjects(A, { format: 'summary' }));

// Release the object.
a = null;
// Search again. queryObjects() includes a full garbage collection
// so a should disappear.
console.log(queryObjects(A)); // 0

class B extends A { bar = 'qux'; }
// The child class B's prototype has A's prototype on its prototype chain
// so the prototype object shows up too.
console.log(queryObjects(A, { format: 'summary' })); // [ A {}' ]

Contributed by Joyee Cheung in #​51927

watch: mark as stable

From this release Watch Mode is considered stable.
When in watch mode, changes in the watched files cause the Node.js process to restart.

Contributed by Moshe Atlow in #​52074

Other Notable Changes
Commits

Configuration

📅 Schedule: Branch creation - "after 7am and before 11am every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update Docker (major) Update Node.js to v19 Oct 29, 2022
@renovate renovate bot changed the title Update Node.js to v19 Update Docker (major) Oct 29, 2022
@renovate renovate bot changed the title Update Docker (major) Update Node.js to v19 Oct 30, 2022
@renovate renovate bot changed the title Update Node.js to v19 Update Docker (major) Oct 30, 2022
@renovate renovate bot force-pushed the renovate/major-docker branch 3 times, most recently from ae653e3 to 9abf11c Compare November 15, 2022 01:08
@renovate renovate bot changed the title Update Docker (major) Update Node.js to v19 Nov 17, 2022
@renovate renovate bot changed the title Update Node.js to v19 Update Docker (major) Nov 17, 2022
@renovate renovate bot force-pushed the renovate/major-docker branch from 9abf11c to 9483b2a Compare November 30, 2022 03:48
@renovate renovate bot changed the title Update Docker (major) Update Node.js to v19 Dec 11, 2022
@renovate renovate bot changed the title Update Node.js to v19 Update Docker (major) Dec 11, 2022
@renovate renovate bot force-pushed the renovate/major-docker branch from 9483b2a to 9a35d53 Compare December 15, 2022 00:16
@renovate renovate bot force-pushed the renovate/major-docker branch from 9a35d53 to e01b445 Compare March 18, 2023 19:59
@renovate renovate bot force-pushed the renovate/major-docker branch from e01b445 to e45995c Compare May 30, 2023 01:45
@renovate renovate bot force-pushed the renovate/major-docker branch from e45995c to 7c6c14a Compare June 9, 2023 23:48
@renovate renovate bot force-pushed the renovate/major-docker branch from 7c6c14a to 0ab8352 Compare June 22, 2023 20:41
@renovate renovate bot force-pushed the renovate/major-docker branch from 0ab8352 to 0e4a69a Compare July 11, 2023 20:48
@renovate renovate bot force-pushed the renovate/major-docker branch from 0e4a69a to 9a642d5 Compare July 22, 2023 02:31
@renovate renovate bot force-pushed the renovate/major-docker branch 2 times, most recently from e01a3e1 to 53b8667 Compare August 12, 2023 08:17
@renovate renovate bot force-pushed the renovate/major-docker branch 2 times, most recently from cf7d0b5 to cc5717b Compare September 12, 2023 23:31
@renovate renovate bot force-pushed the renovate/major-docker branch 2 times, most recently from a829bcf to 95f84c3 Compare September 20, 2023 05:38
@renovate renovate bot force-pushed the renovate/major-docker branch from 95f84c3 to bbc7dd6 Compare September 30, 2023 05:47
@renovate renovate bot force-pushed the renovate/major-docker branch 2 times, most recently from b9a47a3 to fa164b4 Compare October 20, 2023 05:00
@renovate renovate bot force-pushed the renovate/major-docker branch from fa164b4 to 90735e4 Compare October 26, 2023 08:52
@renovate renovate bot force-pushed the renovate/major-docker branch 2 times, most recently from f0707ab to 0c49625 Compare November 16, 2023 08:41
@renovate renovate bot force-pushed the renovate/major-docker branch from 0c49625 to bc7cb4e Compare December 4, 2023 05:51
@renovate renovate bot force-pushed the renovate/major-docker branch from bc7cb4e to caca7c0 Compare January 12, 2024 02:51
@renovate renovate bot force-pushed the renovate/major-docker branch 2 times, most recently from ae27c18 to e1797a0 Compare February 16, 2024 05:41
@renovate renovate bot force-pushed the renovate/major-docker branch from e1797a0 to a146a9e Compare March 27, 2024 20:51
@renovate renovate bot force-pushed the renovate/major-docker branch from a146a9e to 247f788 Compare April 6, 2024 20:55
@renovate renovate bot force-pushed the renovate/major-docker branch from 247f788 to d85d179 Compare April 14, 2024 17:33
@renovate renovate bot force-pushed the renovate/major-docker branch 2 times, most recently from 3ac584b to 5fc12f9 Compare May 10, 2024 02:56
@renovate renovate bot force-pushed the renovate/major-docker branch from 5fc12f9 to c213006 Compare May 29, 2024 08:40
@renovate renovate bot force-pushed the renovate/major-docker branch from c213006 to d342410 Compare June 25, 2024 23:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants