react: v0.4.0

0.4.0 (2026-08-02)

⚠ BREAKING CHANGES

• apps on this release require @frondruntime/hub at the matching version. A 0.3.x hub refuses the attachment with a message naming both versions, rather than accepting it and silently dropping the stream.

Features

• typed signal lane, hub protocol 2, and the lint gate (#18) (7363e4e)

Dependencies

• The following workspace dependencies were updated
  • devDependencies
    • @frondruntime/core bumped to 0.4.0
  • peerDependencies
    • @frondruntime/core bumped from 0.3.0 to 0.4.0

hub: v0.4.0

0.4.0 (2026-08-02)

⚠ BREAKING CHANGES

• apps on this release require @frondruntime/hub at the matching version. A 0.3.x hub refuses the attachment with a message naming both versions, rather than accepting it and silently dropping the stream.

Features

• typed signal lane, hub protocol 2, and the lint gate (#18) (7363e4e)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @frondruntime/core bumped from 0.3.0 to 0.4.0
    • @frondruntime/devtools bumped from 0.3.0 to 0.4.0
    • @frondruntime/react bumped from 0.3.0 to 0.4.0

devtools: v0.4.0

0.4.0 (2026-08-02)

⚠ BREAKING CHANGES

• apps on this release require @frondruntime/hub at the matching version. A 0.3.x hub refuses the attachment with a message naming both versions, rather than accepting it and silently dropping the stream.

Features

• typed signal lane, hub protocol 2, and the lint gate (#18) (7363e4e)

Dependencies

• The following workspace dependencies were updated
  • devDependencies
    • @frondruntime/core bumped to 0.4.0
  • peerDependencies
    • @frondruntime/core bumped from 0.3.0 to 0.4.0

core: v0.4.0

0.4.0 (2026-08-02)

⚠ BREAKING CHANGES

• apps on this release require @frondruntime/hub at the matching version. A 0.3.x hub refuses the attachment with a message naming both versions, rather than accepting it and silently dropping the stream.

Features

• typed signal lane, hub protocol 2, and the lint gate (#18) (7363e4e)

react: v0.3.0

0.3.0 (2026-07-28)

Miscellaneous Chores

• react: Synchronize frondruntime versions

Dependencies

• The following workspace dependencies were updated
  • devDependencies
    • @frondruntime/core bumped to 0.3.0
  • peerDependencies
    • @frondruntime/core bumped from 0.2.0 to 0.3.0

hub: v0.3.0

0.3.0 (2026-07-28)

⚠ BREAKING CHANGES

• devtools: EncodedNodeSnapshot drops label and key, so HUB_PROTOCOL_VERSION moves to 3. label was a presentation formatting of tag and key is already embedded in nodeId; both were duplicated on every row of a graph read. kind stays — "node" versus "resource" is not recoverable from either and decides whether release semantics apply.

Features

• devtools: runtime devtools, the frond-hub daemon, and MCP state reads (#16) (0f3947e)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @frondruntime/core bumped from 0.2.0 to 0.3.0
    • @frondruntime/devtools bumped from 0.2.0 to 0.3.0
    • @frondruntime/react bumped from 0.2.0 to 0.3.0

devtools: v0.3.0

0.3.0 (2026-07-28)

⚠ BREAKING CHANGES

• devtools: EncodedNodeSnapshot drops label and key, so HUB_PROTOCOL_VERSION moves to 3. label was a presentation formatting of tag and key is already embedded in nodeId; both were duplicated on every row of a graph read. kind stays — "node" versus "resource" is not recoverable from either and decides whether release semantics apply.

Features

• devtools: runtime devtools, the frond-hub daemon, and MCP state reads (#16) (0f3947e)

Dependencies

• The following workspace dependencies were updated
  • devDependencies
    • @frondruntime/core bumped to 0.3.0
  • peerDependencies
    • @frondruntime/core bumped from 0.2.0 to 0.3.0

core: v0.3.0

0.3.0 (2026-07-28)

Miscellaneous Chores

• core: Synchronize frondruntime versions

react: v0.2.0

0.2.0 (2026-07-27)

⚠ BREAKING CHANGES

• node authoring moves to serviceSpec.async/.effect(...) with flattened driver hooks; Driver.Async and Driver.Effect are removed from the public Driver namespace. Node and handle action calls are mode-native (the .async/.effect channels and handle.runAction are removed); use unwrapEffect/wrapPromise to cross the Promise/Effect boundary.

Features

• mode-declared spec shapes, mode-native actions, lifecycle hardening (0.2.0) (#13) (2b98dfb)

Dependencies

• The following workspace dependencies were updated
  • devDependencies
    • @frondruntime/core bumped to 0.2.0
  • peerDependencies
    • @frondruntime/core bumped from 0.1.0 to 0.2.0

core: v0.2.0

0.2.0 (2026-07-27)

⚠ BREAKING CHANGES

• node authoring moves to serviceSpec.async/.effect(...) with flattened driver hooks; Driver.Async and Driver.Effect are removed from the public Driver namespace. Node and handle action calls are mode-native (the .async/.effect channels and handle.runAction are removed); use unwrapEffect/wrapPromise to cross the Promise/Effect boundary.

Features

• mode-declared spec shapes, mode-native actions, lifecycle hardening (0.2.0) (#13) (2b98dfb)