chore(deps): update dependency @node-datachannel/win32-arm64-msvc to v0.33.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@node-datachannel/win32-arm64-msvc	0.33.2 → 0.33.4

---

Release Notes

murat-dogan/node-datachannel (@​node-datachannel/win32-arm64-msvc)

v0.33.4

Compare Source

What's Changed

• Add npm-artifacts folder to npmignore by @​longnguyen2004 in #​438
• build: bump libdatachannel to v0.24.5 (fixes intermittent DTLS handshake failures) by @​johnhenry in #​444

New Contributors

• @​johnhenry made their first contribution in #​444

Full Changelog: murat-dogan/node-datachannel@v0.33.1...v0.33.4

v0.33.3

Compare Source

---

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

• Branch creation
  • Only on Monday (* * * * 1)
• 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.

[cloudflare-workers-and-pages]

Deploying mouseterm with    Cloudflare Pages

Latest commit:	f7d3b1a
Status:	✅  Deploy successful!
Preview URL:	https://80eb07b2.mouseterm.pages.dev
Branch Preview URL:	https://renovate-node-datachannel-wi.mouseterm.pages.dev

View logs

[dormouse-bot]

Feedback on work in progress — this is a draft, so it's not a merge verdict.

This bump can't go green on its own, and Build & Test is already red on it for exactly that reason: the Dependency disclosure is current step failed (job log).

generate-deps.js describes the five platform prebuilds pnpm didn't install on the Linux runner from whichever sibling it did install, matching on the exact version string — optionalSiblingsAtSameVersion filters standalone/sidecar/package.json's optionalDependencies for optionalDependencies[name] === version. Moving @node-datachannel/win32-arm64-msvc to 0.33.4 while the other five stay at 0.33.2 leaves that filter returning nothing, and the describe loop throws "…win32-arm64-msvc" is not installed and neither is any sibling declared beside it at the same version, so it cannot be described. That's the rule in docs/specs/security-supply-chain.md → "Disclosure": "described from a sibling in the same optionalDependencies block at the same exact version string".

Even setting CI aside, the bump wouldn't take effect: node-datachannel@0.33.2 declares its own @node-datachannel/win32-arm64-msvc: 0.33.2, and per the comment in standalone/scripts/build-sidecar-proxy.mjs the addon "resolves its platform package and detect-libc relative to its own __dirname" — so the Windows ARM64 loader reaches the 0.33.2 copy, and 0.33.4 rides along unloaded.

The family has to move as one unit — the core node-datachannel package and all six prebuilds together. That's what #642 sets up, and the same failure is sitting on #637, #639, #640, and #643. Landing #642 first and letting Renovate re-open one grouped PR retires all five; closing this one on its own just brings it back next Monday.