Release phyx.js v1.3.0

[gaurav]

Prepares the release of phyx.js v1.3.0, following the steps in RELEASE.md.

TODO before merging

• Regenerate docs/. RELEASE.md step 4 says to regenerate and commit the docs/ tree; that is deliberately not in this PR, pending Replace esdoc with jsdoc and clean-jsdoc-theme #166 (replace esdoc with jsdoc + clean-jsdoc-theme). If Replace esdoc with jsdoc and clean-jsdoc-theme #166 lands first, regenerate with the new toolchain and commit here. If Replace esdoc with jsdoc and clean-jsdoc-theme #166 slips, run npm run docs and commit the esdoc output instead.

  Landing Replace esdoc with jsdoc and clean-jsdoc-theme #166 would also clear most of the current npm audit findings — esdoc is unmaintained and is the sole path to the vulnerable taffydb, nth-check, tough-cookie, uuid and qs versions.

• Fix the phyx2owl failure on Node 26. npm test is green except for one failure in test/scripts/phyx2owl.js ("should be able to convert the entire test/examples/correct directory"), which reproduces on Node 26 both before and after this PR's dependency changes — it is not caused by the upgrade.

  The cause is a mismatch between the bundled undici v6 Agent that jsonld's document loader passes as a dispatcher and Node 26's internal undici, which now supplies an onError handler the v6 dispatcher rejects:

  TypeError: fetch failed
    cause: InvalidArgumentError: invalid onError method (UND_ERR_INVALID_ARG)
      at Agent.dispatch (node_modules/undici/lib/dispatcher/dispatcher-base.js:189:15)
      at httpNetworkFetch (node:internal/deps/undici/undici:14406:73)
  

  Note that pinning undici back to 6.24.1 does not fix it — I tested that explicitly, so the fix isn't simply reverting this PR's undici 6.24.1 → 6.27.0 bump. Any pin would have to be further up the chain (jsonld / @digitalbazaar/http-client) or on Node itself.

  CI covers Node 22/24/25 only, so this should stay green here. But it does mean toRDF() is currently broken on Node 26 for any document that has to dereference a remote context, not just in tests — so this is worth a real fix rather than only a test workaround. Adding 26.x to the CI matrix once fixed would stop it regressing.

What's in here

• npm upgrade — only transitive dependencies moved; every direct dependency was already at the newest version its range allows. Biome stays pinned at 2.4.4 deliberately (2.5.5 is available).
• CHANGELOG.md — the [Unreleased] section was empty, so the ten PRs merged since v1.2.1 have been written up into a new [1.3.0] section. Also fixes the stale [Unreleased] compare link, which still pointed at v1.2.0...master.
• package.json — version bumped to 1.3.0.
• PHYX_CONTEXT_JSON — already updated to context v1.1.0 in Updated PHYX_CONTEXT_JSON to v1.1.0 #171, no change needed here.

Why 1.3.0 and not 1.2.2

Two changes in this release are more than internal churn:

• Updated PHYX_CONTEXT_JSON to v1.1.0 #171 repointed PHYX_CONTEXT_JSON at Phyx JSON-LD context v1.1.0, which changes the JSON-LD this library emits.
• Upgrade jsonld #160 upgraded jsonld across a major version (v8 → v9).

Under semver that reads as a minor release rather than a patch.

🤖 Generated with Claude Code