Skip Hyperswarm test in Deno to fix release pipeline

[Copilot]

Deno CI fails when running hyperswarm-sync.test.ts because importing the hyperswarm package pulls in udx-native, a Node.js native module:

deno: symbol lookup error: .../udx-native.node: undefined symbol: uv_interface_addresses

Changes

• Set ignore: true on the "GunDB.enableSync - throws error in Deno environment" test
• Test was verifying Deno incompatibility anyway; runtime enforces the behavior

Test Safety

Other enableSync() tests remain enabled—they throw validation errors before importing hyperswarm:

• Invalid key validation (regex check)
• Database ready check

Both exit early without triggering the problematic import.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Fix release pipeline</issue_title>
<issue_description>The job failed due to the following error in the logs:

deno: symbol lookup error: /home/runner/work/pluresdb/pluresdb/node_modules/udx-native/prebuilds/linux-x64/udx-native.node: undefined symbol: uv_interface_addresses

This error indicates a native dependency issue, likely caused by running tests in a Deno environment that expects Node.js-specific modules such as udx-native. The relevant test in legacy/tests/unit/hyperswarm-sync.test.ts also checks for this, and expects a Deno environment to throw errors for Hyperswarm-based sync, which relies on Node.js.

Solution:

1. Update the workflow/job definition to skip (ignore) the tests in hyperswarm-sync.test.ts when running in Deno (or any CI using Deno). You can use Deno.test({ignore: true}) for these tests, or conditionally run them only in Node.js environments.
2. Alternatively, adjust the dependencies: Ensure udx-native and related modules are not required or imported during Deno CI runs.

Code suggestion: In your test file, wrap Hyperswarm-dependent tests as ignored in Deno:

Deno.test({
  name: "GunDB.enableSync - throws error in Deno environment",
  ignore: true, // set this to true to skip in Deno CI
  async fn() {
    // ... test code ...
  },
});

And for CI, set an environment variable to skip these tests, or split Node.js and Deno workflows.

This will allow your job to succeed by avoiding tests and imports that can never work in the Deno runner context.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Fix release pipeline #79

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.