chore: update versions

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@stackables/bridge-compiler@2.4.0

Minor Changes

• #104 b213e9f Thanks @copilot-swe-agent! - Multi-Level Control Flow (break N, continue N)

  When working with deeply nested arrays (e.g., mapping categories that contain lists of products), you may want an error deep inside the inner array to skip the outer array element.

  You can append a number to break or continue to specify how many loop levels the signal should pierce.

• #102 2243c7e Thanks @copilot-swe-agent! - Sync tool optimisation — honour the sync flag in ToolMetadata

  When a tool declares { sync: true } in its .bridge metadata the engine
  now enforces and optimises it:

  1. Enforcement — if a sync-declared tool returns a Promise, both the
     runtime and compiled engines throw immediately.
  2. Core optimisation — callTool() skips timeout racing, the OTel span
     wrapper, and all promise handling for sync tools.
  3. Compiler optimisation — generated code uses a dedicated __callSync()
     helper at every call-site, avoiding await overhead entirely.
  4. Array-map fast path — when all per-element tools in an array map are
     sync, the compiled engine generates a dual-path: a synchronous .map()
     branch (no microtask ticks) with a runtime fallback to for…of + await
     for async tools.

  Benchmarks show up to ~50 % latency reduction for compiled array maps
  with sync tools (100 elements).

Patch Changes

• #103 fc6c619 Thanks @aarne! - Fix AOT compiler to throw BridgeTimeoutError on tool timeout

  AOT-compiled bridges now throw BridgeTimeoutError (with the same name and
  message format as the runtime) when a tool exceeds toolTimeoutMs. Previously
  the generated code constructed a generic Error, causing a class mismatch when
  callers caught and inspected the error type.

• #103 fc6c619 Thanks @aarne! - Fix AOT/runtime parity for null element traversal, catch-null recovery, and non-array source handling

• Updated dependencies [b213e9f, fc6c619, fc6c619, 2243c7e, 8e5b2e2]:

  • @stackables/bridge-core@1.5.0
  • @stackables/bridge-stdlib@1.5.2

@stackables/bridge-core@1.5.0

Minor Changes

• #104 b213e9f Thanks @copilot-swe-agent! - Multi-Level Control Flow (break N, continue N)

  When working with deeply nested arrays (e.g., mapping categories that contain lists of products), you may want an error deep inside the inner array to skip the outer array element.

  You can append a number to break or continue to specify how many loop levels the signal should pierce.

• #102 2243c7e Thanks @copilot-swe-agent! - Sync tool optimisation — honour the sync flag in ToolMetadata

  When a tool declares { sync: true } in its .bridge metadata the engine
  now enforces and optimises it:

  1. Enforcement — if a sync-declared tool returns a Promise, both the
     runtime and compiled engines throw immediately.
  2. Core optimisation — callTool() skips timeout racing, the OTel span
     wrapper, and all promise handling for sync tools.
  3. Compiler optimisation — generated code uses a dedicated __callSync()
     helper at every call-site, avoiding await overhead entirely.
  4. Array-map fast path — when all per-element tools in an array map are
     sync, the compiled engine generates a dual-path: a synchronous .map()
     branch (no microtask ticks) with a runtime fallback to for…of + await
     for async tools.

  Benchmarks show up to ~50 % latency reduction for compiled array maps
  with sync tools (100 elements).

• #100 8e5b2e2 Thanks @aarne! - Add ToolMetadata — per-tool observability controls

  Tools can now attach a .bridge property to declare how the engine should
  instrument them, imported as ToolMetadata from @stackables/bridge.

  import type { ToolMetadata } from "@stackables/bridge";
  
  myTool.bridge = {
    trace: false, // skip OTel span for this tool
    log: {
      execution: "info", // log successful calls at info level
      errors: "error", // log failures at error level (default)
    },
  } satisfies ToolMetadata;

Patch Changes

• #103 fc6c619 Thanks @aarne! - Fix AOT/runtime parity for null element traversal, catch-null recovery, and non-array source handling

• Updated dependencies [fc6c619, 8e5b2e2]:

  • @stackables/bridge-stdlib@1.5.2
  • @stackables/bridge-types@1.1.0

@stackables/bridge-graphql@1.2.0

Minor Changes

• #104 b213e9f Thanks @copilot-swe-agent! - Support optional lookahead resolver with compiler

Patch Changes

• Updated dependencies [b213e9f, fc6c619, fc6c619, 2243c7e, 8e5b2e2]:
  • @stackables/bridge-core@1.5.0
  • @stackables/bridge-stdlib@1.5.2

@stackables/bridge-parser@1.4.0

Minor Changes

• #104 b213e9f Thanks @copilot-swe-agent! - Multi-Level Control Flow (break N, continue N)

  When working with deeply nested arrays (e.g., mapping categories that contain lists of products), you may want an error deep inside the inner array to skip the outer array element.

  You can append a number to break or continue to specify how many loop levels the signal should pierce.

Patch Changes

• Updated dependencies [b213e9f, fc6c619, fc6c619, 2243c7e, 8e5b2e2]:
  • @stackables/bridge-core@1.5.0
  • @stackables/bridge-stdlib@1.5.2

@stackables/bridge-types@1.1.0

Minor Changes

• #100 8e5b2e2 Thanks @aarne! - Add ToolMetadata — per-tool observability controls

  Tools can now attach a .bridge property to declare how the engine should
  instrument them, imported as ToolMetadata from @stackables/bridge.

  import type { ToolMetadata } from "@stackables/bridge";
  
  myTool.bridge = {
    trace: false, // skip OTel span for this tool
    log: {
      execution: "info", // log successful calls at info level
      errors: "error", // log failures at error level (default)
    },
  } satisfies ToolMetadata;

@stackables/bridge@2.2.1

Patch Changes

• Updated dependencies [b213e9f, b213e9f, fc6c619, fc6c619, 2243c7e, 8e5b2e2]:
  • @stackables/bridge-parser@1.4.0
  • @stackables/bridge-core@1.5.0
  • @stackables/bridge-graphql@1.2.0
  • @stackables/bridge-stdlib@1.5.2

@stackables/bridge-stdlib@1.5.2

Patch Changes

• #103 fc6c619 Thanks @aarne! - Fix filter, find, toLowerCase, toUpperCase, trim, and length crashing on unexpected input types

• #100 8e5b2e2 Thanks @aarne! - Add ToolMetadata — per-tool observability controls

  Tools can now attach a .bridge property to declare how the engine should
  instrument them, imported as ToolMetadata from @stackables/bridge.

  import type { ToolMetadata } from "@stackables/bridge";
  
  myTool.bridge = {
    trace: false, // skip OTel span for this tool
    log: {
      execution: "info", // log successful calls at info level
      errors: "error", // log failures at error level (default)
    },
  } satisfies ToolMetadata;

• Updated dependencies [8e5b2e2]:

  • @stackables/bridge-types@1.1.0

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	bridge	f0802f3	Commit Preview URL Branch Preview URL	Mar 06 2026, 02:35 PM