chore: update versions

Author: github-actions[bot]

.changeset/aot-timeout-error-class.md

@@ -1,5 +1,60 @@
 # @stackables/bridge-compiler
 
+## 2.4.0
+
+### Minor Changes
+
+- [#104](https://github.com/stackables/bridge/pull/104) [`b213e9f`](https://github.com/stackables/bridge/commit/b213e9f49ed5da80e7d9a1b9e161586e59b3719c) Thanks [@copilot-swe-agent](https://github.com/apps/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
+
+- [#103](https://github.com/stackables/bridge/pull/103) [`fc6c619`](https://github.com/stackables/bridge/commit/fc6c6195dec524c880ac20f3057e776f76583f60) Thanks [@aarne](https://github.com/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](https://github.com/stackables/bridge/pull/103) [`fc6c619`](https://github.com/stackables/bridge/commit/fc6c6195dec524c880ac20f3057e776f76583f60) Thanks [@aarne](https://github.com/aarne)! - Fix AOT/runtime parity for null element traversal, catch-null recovery, and non-array source handling
+
+  **bridge-core:**
+
+  - `catch` gate now correctly recovers with an explicit `null` fallback value.
+    Previously, `if (recoveredValue != null)` caused the catch gate to rethrow
+    the original error when the fallback resolved to `null`; changed to
+    `!== undefined` so `null` is treated as a valid recovered value.
+
+  - Element refs (array-mapping `el.field` references) are now null-safe during
+    path traversal. When an array element is `null` or `undefined`, the runtime
+    returns `undefined` instead of throwing `TypeError`, matching AOT-generated
+    code which uses optional chaining on element accesses.
+
+  - Array-mapping fields (`resolveNestedField`) now return `null` when the
+    resolved source value is not an array, instead of returning the raw value
+    unchanged. This aligns with AOT behavior and makes non-array source handling
+    consistent.
+
+  **bridge-compiler:**
+
+  - AOT-generated code now respects `rootSafe` / `pathSafe` flags on input refs,
+    using strict property access (`["key"]`) instead of optional chaining
+    (`?.["key"]`) for non-safe segments. Previously all input-ref segments used
+    optional chaining regardless of flags, silently swallowing TypeErrors that
+    the runtime would throw.
+
+  - Array-mapping expressions now guard the source with `Array.isArray` before
+    calling `.map` / `.flatMap`. Previously, a non-array non-null source
+    (e.g. a string) would cause a `TypeError` in the generated code while the
+    runtime returned `null`.
+
+- Updated dependencies [[`b213e9f`](https://github.com/stackables/bridge/commit/b213e9f49ed5da80e7d9a1b9e161586e59b3719c), [`fc6c619`](https://github.com/stackables/bridge/commit/fc6c6195dec524c880ac20f3057e776f76583f60), [`fc6c619`](https://github.com/stackables/bridge/commit/fc6c6195dec524c880ac20f3057e776f76583f60), [`8e5b2e2`](https://github.com/stackables/bridge/commit/8e5b2e21796cfd7e9a9345225d94ceb8bfc39bac)]:
+  - @stackables/bridge-core@1.5.0
+  - @stackables/bridge-stdlib@1.5.2
+
 ## 2.3.0
 
 ### Minor Changes

.changeset/fifty-cases-rhyme.md

@@ -1,6 +1,6 @@
 {
   "name": "@stackables/bridge-compiler",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "description": "Compiles a BridgeDocument into highly optimized JavaScript code",
   "main": "./build/index.js",
   "type": "module",

.changeset/many-beds-like.md

@@ -1,5 +1,70 @@
 # @stackables/bridge-core
 
+## 1.5.0
+
+### Minor Changes
+
+- [#104](https://github.com/stackables/bridge/pull/104) [`b213e9f`](https://github.com/stackables/bridge/commit/b213e9f49ed5da80e7d9a1b9e161586e59b3719c) Thanks [@copilot-swe-agent](https://github.com/apps/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.
+
+- [#100](https://github.com/stackables/bridge/pull/100) [`8e5b2e2`](https://github.com/stackables/bridge/commit/8e5b2e21796cfd7e9a9345225d94ceb8bfc39bac) Thanks [@aarne](https://github.com/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`.
+
+  ```ts
+  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](https://github.com/stackables/bridge/pull/103) [`fc6c619`](https://github.com/stackables/bridge/commit/fc6c6195dec524c880ac20f3057e776f76583f60) Thanks [@aarne](https://github.com/aarne)! - Fix AOT/runtime parity for null element traversal, catch-null recovery, and non-array source handling
+
+  **bridge-core:**
+
+  - `catch` gate now correctly recovers with an explicit `null` fallback value.
+    Previously, `if (recoveredValue != null)` caused the catch gate to rethrow
+    the original error when the fallback resolved to `null`; changed to
+    `!== undefined` so `null` is treated as a valid recovered value.
+
+  - Element refs (array-mapping `el.field` references) are now null-safe during
+    path traversal. When an array element is `null` or `undefined`, the runtime
+    returns `undefined` instead of throwing `TypeError`, matching AOT-generated
+    code which uses optional chaining on element accesses.
+
+  - Array-mapping fields (`resolveNestedField`) now return `null` when the
+    resolved source value is not an array, instead of returning the raw value
+    unchanged. This aligns with AOT behavior and makes non-array source handling
+    consistent.
+
+  **bridge-compiler:**
+
+  - AOT-generated code now respects `rootSafe` / `pathSafe` flags on input refs,
+    using strict property access (`["key"]`) instead of optional chaining
+    (`?.["key"]`) for non-safe segments. Previously all input-ref segments used
+    optional chaining regardless of flags, silently swallowing TypeErrors that
+    the runtime would throw.
+
+  - Array-mapping expressions now guard the source with `Array.isArray` before
+    calling `.map` / `.flatMap`. Previously, a non-array non-null source
+    (e.g. a string) would cause a `TypeError` in the generated code while the
+    runtime returned `null`.
+
+- Updated dependencies [[`fc6c619`](https://github.com/stackables/bridge/commit/fc6c6195dec524c880ac20f3057e776f76583f60), [`8e5b2e2`](https://github.com/stackables/bridge/commit/8e5b2e21796cfd7e9a9345225d94ceb8bfc39bac)]:
+  - @stackables/bridge-stdlib@1.5.2
+  - @stackables/bridge-types@1.1.0
+
 ## 1.4.0
 
 ### Minor Changes

.changeset/runtime-parity-fixes.md

@@ -1,6 +1,6 @@
 {
   "name": "@stackables/bridge-core",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "description": "Bridge runtime engine — execute pre-compiled bridge instructions",
   "main": "./build/index.js",
   "type": "module",