Skip to content

Conversation

ggrossetie
Copy link
Owner

@ggrossetie ggrossetie commented Nov 1, 2024

This PR contains the following updates:

Package Type Update Change
node final major 16.16.0-bullseye-slim -> 23.11.0-bullseye-slim

Release Notes

nodejs/node (node)

v23.11.0: 2025-04-01, Version 23.11.0 (Current), @​aduh95

Compare Source

Notable Changes
  • [64b086740a] - (SEMVER-MINOR) assert: implement partial error comparison (Ruben Bridgewater) #​57370
  • [053cef70e0] - (SEMVER-MINOR) crypto: add optional callback to crypto.diffieHellman (Filip Skokan) #​57274
  • [f8aff90235] - (SEMVER-MINOR) process: add execve (Paolo Insogna) #​56496
  • [4b04c92d7d] - (SEMVER-MINOR) sqlite: add StatementSync.prototype.columns() (Colin Ihrig) #​57490
  • [1b8d1d3a3a] - (SEMVER-MINOR) util: expose diff function used by the assertion errors (Giovanni Bucci) #​57462
Commits

v23.10.0: 2025-03-13, Version 23.10.0 (Current), @​aduh95

Compare Source

Notable Changes
Introducing --experimental-config-file

With the introduction of test runner, SEA, and other feature that require a lot
of flags, a JSON config flag would improve by a lot the developer experience and
increase adoption.

You can have a node.config.json containing:

{
  "$schema": "https://nodejs.org/dist/v23.10.0/docs/node-config-schema.json",
  "nodeOptions": {
    "test-coverage-lines": 80,
    "test-coverage-branches": 60
  }
}

You can run your tests without passing the flags defined in the config file.

node --experimental-default-config-file --test --experimental-test-coverage

or

node --experimental-config-file=node.config.json --test --experimental-test-coverage

Node.js will not sanitize or perform validation on the user-provided configuration,
so only ever use trusted configuration files.

Contributed by Marco Ippolito in #​57016
and #​57171.

Other Notable Changes
Commits

v23.9.0: 2025-02-26, Version 23.9.0 (Current), @​targos

Compare Source

Notable Changes
Commits

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), 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 this update again.


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

This PR has been generated by Renovate Bot.

@ggrossetie ggrossetie force-pushed the renovate/node-23.x branch 2 times, most recently from 7fc5ae8 to 07c2305 Compare November 22, 2024 02:34
@ggrossetie ggrossetie changed the title Update dependency node to v23 Update node Docker tag to v23 Jan 27, 2025
@ggrossetie ggrossetie force-pushed the renovate/node-23.x branch from eb34494 to 7604acf Compare April 6, 2025 16:09
@ggrossetie ggrossetie changed the title Update node Docker tag to v23 Update node Docker tag to v23 - autoclosed May 7, 2025
@ggrossetie ggrossetie closed this May 7, 2025
@ggrossetie ggrossetie deleted the renovate/node-23.x branch May 7, 2025 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant