nodejs_20: 20.14.0 -> 20.15.0

[aduh95]

Description of changes

https://github.com/nodejs/node/releases/tag/v20.15.0

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[aduh95]

Cherry-picked a commit to account for the failing tests, see #313982 (comment)

[drupol]

Can you squash all your commits into one single commit?

[github-actions]

Backport failed for release-24.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-24.05
git worktree add -d .worktree/backport-321292-to-release-24.05 origin/release-24.05
cd .worktree/backport-321292-to-release-24.05
git switch --create backport-321292-to-release-24.05
git cherry-pick -x c1a9808e31ab0be4f63d61f0e863d7a29d3bcc98

[vcunat]

You ticked that it builds on aarch64-darwin? Before this update it won't build (#322145, example hydra build) and this update doesn't seem to fix that (tried locally).

[vcunat]

It's possible that something else in master..staging-next broke this, of course. (and you e.g. built atop master)

[aduh95]

Yes you're right, I tried locally on top of master, then remembered I have to target staging for this package, and did not re-try the build after the rebase.

[vcunat]

Not a problem. I think it's usually better, as building against staging head would typically have a bad ratio of work/benefit. (staging-next sometimes, but depends on timing...)

[vcunat]

Though of course, it will be great if someone fixes the issue, even if not introduced by this update.

[aduh95]

I think that's what #262124 is up to :)