chore(deps): update dependency @node-datachannel/linux-x64-gnu to v0.33.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@node-datachannel/linux-x64-gnu	0.33.2 → 0.33.4

---

Release Notes

murat-dogan/node-datachannel (@​node-datachannel/linux-x64-gnu)

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:	ec527cb
Status:	✅  Deploy successful!
Preview URL:	https://83d5de88.mouseterm.pages.dev
Branch Preview URL:	https://renovate-node-datachannel-li-ogro.mouseterm.pages.dev

View logs

[dormouse-bot]

Feedback on a draft — not a merge verdict.

The bump itself is a clean single-package edit, but it cannot go green on its own and it would not deliver the upstream fix if it did.

Build & Test is already red on the Dependency disclosure is current step: "@node-datachannel/darwin-arm64" is not installed and neither is any sibling declared beside it at the same version, so it cannot be described. website/scripts/generate-deps.js describes the five prebuilds pnpm did not install from whichever sibling it did, matching on the exact version string — the "optional, declared by a product root" rule in docs/specs/security-supply-chain.md -> Disclosure. Moving @node-datachannel/linux-x64-gnu to 0.33.4 while the other five stay at 0.33.2 leaves the uninstalled ones with no installed same-version sibling, so the generator throws.

Separately, the release this bump is for (libdatachannel v0.24.5, the intermittent DTLS handshake fix) would not reach the runtime even with the disclosure step passing. standalone/sidecar/package.json still pins core node-datachannel at 0.33.2, and that package declares @node-datachannel/linux-x64-gnu: 0.33.2 in its own optionalDependencies (pnpm-lock.yaml, the node-datachannel@0.33.2 snapshot). The addon resolves its .node relative to its own directory, so on Linux x64 the nested 0.33.2 binary is what loads and the 0.33.4 copy at the sidecar root is bundled unused.

The whole family has to move together. #642 adds the Renovate lockstep group for node-datachannel plus @node-datachannel/**; once it lands, the next Monday run replaces this PR and its siblings (#637, #639, #640, #644) with a single grouped bump. Closing this one in favour of that is the cheaper path than patching the other six versions onto this branch by hand, which Renovate would overwrite on its next run anyway.