v3.6.1

What's new

A single security-scoped patch drives this release: a High-severity denial-of-service advisory in the js-yaml parser is patched, alongside routine automated dependency maintenance.

Bug Fixes

• security: js-yaml is bumped from the resolved 4.3.0 to 4.3.1, patching GHSA-5p4m-2wfm-xmqj (CVE-2026-59870, CVSS 7.5, High). The advisory is in resolveYamlOmap(), whose key-uniqueness check does a linear scan per element when resolving YAML !!omap sequences — making the operation O(n²) overall. Because !!omap is part of the default YAML schema, any yaml.load() call is exposed without special options; a roughly 2.5MB crafted document can block the Node.js event loop for around 10 seconds. js-yaml is used directly in src/lib/frontmatter.ts to parse skill, agent, and command frontmatter, so this was real attack surface for anyone feeding untrusted skill/agent files through Systematic.

  4.3.1 back-ports the same Set-based key-tracking fix already shipped in the 5.x line (since 5.2.1) and satisfies the existing ^4.1.1 semver range in package.json, so the fix is a lockfile-scoped patch bump with no source changes required. It is independent of the pending major-version migration tracked in #733 (js-yaml v5), which additionally requires an import-shape fix for a dropped default export and is left to the normal Renovate/category-1 repair path.

  Verified on the fix branch: typecheck, lint, bun test tests/unit (1827 pass), build, content-integrity, and an ESM default-export smoke test all passed.

Also in this release

• deps: Renovate-driven updates — OpenCode bumped through v1.18.12 → v1.18.16, fro-bot/agent through v0.96.2 → v0.98.4, bfra-me/.github to v4.16.45, @types/node to v26.2.0, typebox to v1.3.10 and v1.3.11, @biomejs/biome to v2.5.7, semantic-release to v25.0.9, and a batched non-major dependency update.

Compare

v3.6.0...v3.6.1