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

chore(deps): update node.js to v23.4.0 - autoclosed #385

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 21, 2024

This PR contains the following updates:

Package Type Update Change
node (source) engines minor 23.2.0 -> v23.4.0

Release Notes

nodejs/node (node)

v23.4.0: 2024-12-10, Version 23.4.0 (Current), @​aduh95 prepared by @​targos

Compare Source

Notable Changes
Introducing experimental assert.partialDeepStrictEqual

Sometimes, when writing test, we want to validate that some specific properties
are present, and the mere presence of additional keys are not exactly relevant
for that specific test. For this use case, we can now use
assert.partialDeepStrictEqual, which should be familiar to those already using
assert.deepStrictEqual, with the main difference that it does not require all
properties in the actual parameter to be present in the expected parameter.

Here are a few examples of usage:

assert.partialDeepStrictEqual(
  { a: 1, b: 2, c: 3 },
  { a: 1, b: 2 },
);

assert.partialDeepStrictEqual(
  [1, 2, 3, 4],
  [2, 3],
);

assert.partialDeepStrictEqual(
  { a: { b: { c: 1, d: 2 } }, e: 3 },
  { a: { b: { c: 1 } } },
);

assert.partialDeepStrictEqual(
  { a: { b: { c: 1, d: 2 } }, e: 3 },
  { a: { b: { c: 1 } } },
);

assert.partialDeepStrictEqual(
  new Set([{ a: 1 }, { b: 1 }]),
  new Set([{ a: 1 }]),
);

assert.partialDeepStrictEqual(
  { a: new Set([{ a: 1 }, { b: 1 }]), b: new Map(), c: [1, 2, 3] },
  { a: new Set([{ a: 1 }]), c: [2] },
);

Contributed by Giovanni Bucci in #​54630.

Implement --trace-env and --trace-env-[js|native]-stack

This release introduces --trace-env, --trace-env-js-stack and --trace-env-native-stack
CLI options that print information about any access to environment variables done in the current
Node.js instance to stderr. Currently in the logs, only the names of the environment variables
being accessed are printed, while the values are not printed to avoid leaking sensitive
information. To print the stack trace of the access, use --trace-env-js-stack and/or
--trace-env-native-stack.

Contributed by Joyee Cheung in #​55604.

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 this update 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-23.x-lockfile branch from ee258d4 to 8e99368 Compare December 2, 2024 10:23
@renovate renovate bot changed the title chore(deps): update node.js to v23.3.0 chore(deps): update node.js to v23.4.0 Dec 11, 2024
@renovate renovate bot force-pushed the renovate/node-23.x-lockfile branch from 8e99368 to c8f6d7f Compare December 11, 2024 02:23
@yegor256
Copy link
Member

@rultor please, try to merge, since 13 checks have passed

@renovate renovate bot changed the title chore(deps): update node.js to v23.4.0 chore(deps): update node.js to v23.4.0 - autoclosed Dec 11, 2024
@renovate renovate bot closed this Dec 11, 2024
@renovate renovate bot deleted the renovate/node-23.x-lockfile branch December 11, 2024 04:02
@rultor
Copy link
Contributor

rultor commented Dec 11, 2024

@rultor please, try to merge, since 13 checks have passed

@renovate[bot] @yegor256 The pull request is closed already, so I can't merge it.

@rultor
Copy link
Contributor

rultor commented Dec 11, 2024

@rultor please, try to merge, since 13 checks have passed

@yegor256 I'm sorry, I don't understand you :( Check this page and try again please.

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.

2 participants