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.1.0

Minor Changes

• #82 cf5cd2e Thanks @aarne! - Add requestedFields option to executeBridge() for sparse fieldset filtering.

  When provided, only the listed output fields (and their transitive tool dependencies) are resolved.
  Tools that feed exclusively into unrequested fields are never called, reducing latency and upstream
  bandwidth.

  Supports dot-separated paths and a trailing wildcard (["id", "price", "legs.*"]).

Patch Changes

• badbb78 Thanks @aarne! - Fix three code generation bugs that caused SyntaxError: await is only valid in async functions when array mappings combined catch fallbacks or element-scoped tools with control flow.

  • Bug 1 – catch inside array .map(): needsAsync only checked for element-scoped tool calls. Wires with catch fallbacks or catch control flow that fall back to an async IIFE now also trigger the async for...of loop path.

  • Bug 2 – element-scoped tool inside .flatMap(): When a ?? continue (or similar) control flow was detected first, the compiler unconditionally emitted .flatMap(). If the same loop also contained an element-scoped tool (alias tool:iter), the await __call(...) was placed inside a synchronous .flatMap() callback. needsAsync is now evaluated before the control-flow check, and when true, a for...of loop with a native continue statement is emitted instead.

  • Bug 3 – nested sub-array async blindspot: The inner sub-array handler in buildElementBody never calculated needsAsync, always falling back to a synchronous .map(). It now uses the same async for...of IIFE pattern when inner wires contain element-scoped tools or catch expressions.

• #84 837ec1c Thanks @aarne! - Fix several AOT compiler/runtime parity bugs discovered via fuzzing:

  • Fix condAnd and condOr code generation to match runtime boolean semantics.
  • Fix nullish fallback chaining so ?? handling matches runtime overdefinition boundaries.
  • Fix overdefinition precedence so the first constant wire remains terminal, matching runtime behavior.
  • Fix serializeBridge quoting for empty-string and slash-only string constants so parse/serialize/parse round-trips remain valid.
  • Add deterministic regression coverage for these parity cases to prevent regressions.

• Updated dependencies [cf5cd2e]:

  • @stackables/bridge-core@1.2.0

@stackables/bridge-core@1.2.0

Minor Changes

• #82 cf5cd2e Thanks @aarne! - Add requestedFields option to executeBridge() for sparse fieldset filtering.

  When provided, only the listed output fields (and their transitive tool dependencies) are resolved.
  Tools that feed exclusively into unrequested fields are never called, reducing latency and upstream
  bandwidth.

  Supports dot-separated paths and a trailing wildcard (["id", "price", "legs.*"]).

@stackables/bridge@2.1.3

Patch Changes

• Updated dependencies [837ec1c, cf5cd2e]:
  • @stackables/bridge-parser@1.1.1
  • @stackables/bridge-core@1.2.0
  • @stackables/bridge-graphql@1.1.2

@stackables/bridge-graphql@1.1.2

Patch Changes

• Updated dependencies [cf5cd2e]:
  • @stackables/bridge-core@1.2.0

@stackables/bridge-parser@1.1.1

Patch Changes

• #84 837ec1c Thanks @aarne! - Fix several AOT compiler/runtime parity bugs discovered via fuzzing:

  • Fix condAnd and condOr code generation to match runtime boolean semantics.
  • Fix nullish fallback chaining so ?? handling matches runtime overdefinition boundaries.
  • Fix overdefinition precedence so the first constant wire remains terminal, matching runtime behavior.
  • Fix serializeBridge quoting for empty-string and slash-only string constants so parse/serialize/parse round-trips remain valid.
  • Add deterministic regression coverage for these parity cases to prevent regressions.

• Updated dependencies [cf5cd2e]:

  • @stackables/bridge-core@1.2.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	cd9881a	Commit Preview URL Branch Preview URL	Mar 04 2026, 05:58 PM