• v0.15.3 a3d62f2415

    v0.15.3 Stable

    x released this 2026-11-03 00:37:39 +00:00 | 20 commits to main since this release

    VSKI v0.15.3

    Security and reliability release. Upgrade as soon as possible: realtime
    subscriptions now enforce collection access rules (a behavioral change for
    service consumers, see below), and the workflow engine fixes address two
    bugs that could lose or kill jobs.

    Realtime security

    Subscriptions are now authorized like every other surface. The collection's
    list rule is evaluated when subscribing and again for every delivered
    event, per subscriber: records the caller may not read are never sent to
    their socket, and closed collections (rules: null) reject non-admin
    subscriptions outright. Admins bypass rules as elsewhere.

    Rule expressions using x in @request.auth.roles now evaluate correctly;
    previously such rules always denied.

    Behavior change: API-key consumers (plugin instances, service workers)
    subscribing to a collection without a list rule will now be rejected.
    Grant access explicitly, same as for REST:

    collections:
      notes:
        rules:
          list: "*"        # or a role check: "'service' in @request.auth.roles"
    

    Workflow engine

    • WebSocket writes are serialized per worker connection. Subscription
      confirmations and job dispatches previously raced on one connection,
      panicking the handler and surfacing as HTTP 500s on workflow triggers.
    • Nacked jobs are actually redelivered. Nack and the 30s visibility-timeout
      requeue put the job back to pending but never cleared the in-memory
      dispatch marker, so the job was skipped forever and its run hung in
      running. Both paths now clear it.

    SDK fixes (TypeScript)

    • The workflow worker no longer drops jobs that arrive before it finishes
      subscribing: they are nacked and redelivered after 5 seconds instead of
      sitting stuck until the visibility timeout.
    • Execution timeouts above ~24.8 days no longer overflow the JavaScript
      timer ceiling and instantly fail the run with a spurious
      "CircuitBreaker: Execution timeout".
    • API keys are percent-encoded in WebSocket and hook URLs. Keys whose
      base64 contains + previously failed authentication (the + decoded to
      a space), which looked like random 401s depending on the generated key.
    • The Python SDK already encoded tokens correctly and is unaffected.

    Testing

    The e2e harness now uses the in-tree SDK by default (previous default
    pointed at a stale sibling checkout), boots plugins with the SDK venv
    python, and binds helper servers to ephemeral ports. The full suite passes
    47/47, twice in a row.

    Downloads