Release notes from wasmagent-js
Articles about Release notes from wasmagent-js
Release @wasmagent/aisdk@1.1.0 · WasmAgent/wasmagent-js
Minor Changes 273157e: Add ai@7 to the peer range (^4 || ^5 || ^6 || ^7) — AI SDK 7 is now stable. The adapter's structural tool() contract ({description, parameters, execute}) is unchanged; verified against ai@7.0.136 with @ai-sdk/openai@4.0.91 (examples updated to the same pairing, closing the openai@4 upgrade blocked by #482/#520).
Release @wasmagent/model-zhipu@2.0.12 · WasmAgent/wasmagent-js
Patch Changes @wasmagent/models@2.0.12
Release @wasmagent/openai-agents@1.0.19 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [0c92587] @wasmagent/core@3.10.0
Release @wasmagent/react@1.5.6 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [0c92587] @wasmagent/core@3.10.0
Release @wasmagent/otel-exporter@7.1.2 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [0c92587] @wasmagent/core@3.10.0
Release @wasmagent/model-openai@2.0.11 · WasmAgent/wasmagent-js
Patch Changes @wasmagent/models@2.0.11
Release @wasmagent/tools-browser@1.0.18 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [0691d43] @wasmagent/core@3.9.0
Release @wasmagent/models@2.0.11 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [0691d43] @wasmagent/core@3.9.0
Release @wasmagent/otel-exporter@7.1.1 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [0691d43] @wasmagent/core@3.9.0
Release @wasmagent/openai-agents@1.0.18 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [0691d43] @wasmagent/core@3.9.0
Release @wasmagent/otel-exporter@7.1.0 · WasmAgent/wasmagent-js
Minor Changes 24e06db: Align the AEP ↔ OTel bridge with the current OTel GenAI semantic conventions (execute_tool). Emission (aepActionToOtelSpan): action-evidence spans are now named execute_tool (previously tool.call) and carry the current standard attributes gen_ai.operation.name = execute_tool, gen_ai.tool.name and gen_ai.tool.call.id, alongside the existing aep.* extension attributes. aep.state_changing is only emitted when the record actually asserts it.
Release @wasmagent/mcp-gateway@0.1.17 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [bc39531] @wasmagent/mcp-firewall@2.2.1
Release @wasmagent/mcp-firewall@2.2.1 · WasmAgent/wasmagent-js
Patch Changes bc39531: fix(adversarial): schedule/workflow_dispatch runs now record tested_main_sha — scheduled report artifacts no longer fail identity-binding validation (F6).
Release @wasmagent/aep@2.10.0 · WasmAgent/wasmagent-js
Minor Changes 4224f52: Breaking-ish default change (current-truth alignment): AEPEmitter now emits the current schema family aep/v0.5 by DEFAULT — both unsigned build() and DSSE-signed emit() stamp aep/v0.5 when schemaVersion is omitted. Previously the defaults were aep/v0.3 (unsigned) and aep/v0.4 (signed), producing newly-created legacy records from ordinary usage. Per the org contract ("read legacy, emit current"), aep/v0.3 / aep/v0.4 remain available ONLY as an explicit schemaVersion opt-in for legacy compatibility;
Release @wasmagent/mcp-gateway@0.1.16 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [934019e] @wasmagent/mcp-firewall@2.2.0
Release @wasmagent/mcp-firewall@2.2.0 · WasmAgent/wasmagent-js
Minor Changes 934019e: Adversarial hardening waves 1–4: promote to F2 phase Wave 1 — Baseline & corpus (FW-01 to FW-04) Add package-metadata.json as single source of truth for maturity/phase Freeze adversarial corpus: 60 samples across 9 categories, stratified 38/11/11 train/dev/holdout split Add normalize.ts: 11-stage normalization pipeline (URL decode, HTML entity, base64, homoglyph, full-width, zero-width stripping) with bounded decode depths
Release @wasmagent/tools-browser@1.0.17 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [ce63ca5] @wasmagent/core@3.8.0
Release @wasmagent/react@1.5.4 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [ce63ca5] @wasmagent/core@3.8.0
Release @wasmagent/otel-exporter@7.0.1 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [ce63ca5] @wasmagent/core@3.8.0
Release @wasmagent/openai-agents@1.0.17 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [ce63ca5] @wasmagent/core@3.8.0
Release @wasmagent/models@2.0.10 · WasmAgent/wasmagent-js
Patch Changes Updated dependencies [ce63ca5] @wasmagent/core@3.8.0
Release @wasmagent/kernel-wasmtime@1.20.0 · WasmAgent/wasmagent-js
Minor Changes 3abbccc: maxMemoryBytes is now validated as a hard ceiling: non-finite, non-safe-integer, non-positive, or sub-page (< 65536 bytes) values throw a RangeError at construction. WebAssembly memory is page-granular, so a sub-page limit cannot be enforced — the previous behavior silently widened it to one page, contradicting the hard-maximum contract. Patch Changes @wasmagent/core@3.7.0
Release @wasmagent/aep@2.9.0 · WasmAgent/wasmagent-js
Minor Changes 3abbccc: DSSE 1.0.2 base64 verifier interop + current-profile signed-record schema. verifyDSSEEnvelope / verifyAEPRecord now accept both standard and URL-safe base64 alphabets for the envelope payload and signature ("Either standard or URL-safe base64 encodings are allowed ... verifiers MUST accept either"), decoding via a bijection ('-'→'+', '_'→'/') that matches the Rust and Python verifiers byte-for-byte, including unique decoding of mixed alphabets. New decodeBase64Either export with the same semantics.
Release @wasmagent/aep@2.8.2 · WasmAgent/wasmagent-js
Patch Changes 315346d: Regenerate the JSON Schema export from the Zod source of truth. The exported schemas/aep-record.schema.json now includes run-level recording_mode, side_effect_class, and argument_drift (open object) matching the canonical protocol schema, plus uniqueItems: true on run_attribution_backing_observed. The export script post-processes uniqueness refinements, which zod-to-json-schema cannot express; CI's schema:check verifies freshness against this exact pipeline.
Release @wasmagent/aep@2.8.1 · WasmAgent/wasmagent-js
Patch Changes 4f2982a: Align the exported aep-record.schema.json with the canonical protocol schema: adopt run-level argument_drift, recording_mode, and side_effect_class definitions verbatim, and add uniqueItems: true to run_attribution_backing_observed. This resolves all remaining Gate B reconcile drifts; per-action argument_drift remains a documented JS extension. No runtime behavior change.
Release @wasmagent/aep@2.8.0 · WasmAgent/wasmagent-js
Minor Changes cdf945a: DSSE PAE now covers decoded serialized-body bytes (not base64 text), conforming to DSSE 1.0 §2. paeEncode accepts Uint8Array payload; paeEncodeString added for convenience. All existing signatures must be regenerated. cdf945a: DSSE PAE now covers decoded serialized-body bytes per DSSE 1.0.2 §2 (was: base64 text). paeEncode accepts Uint8Array. All existing DSSE signatures must be regenerated.