🦋 New version release#10
Merged
Merged
Conversation
brentrager
force-pushed
the
changeset-release/main
branch
from
50bd0cc to
73a1d52
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
@smooai/smooth-operator@0.6.0
Minor Changes
RedisBackplaneandNatsBackplane— the horizontal scale-out seam. Both implement theBackplanetrait by wrapping a per-podInMemoryBackplanefor local registry + delivery and adding a pub/sub bus (Redis/Valkey channel or NATS subject) for cross-pod fan-out:publish(Target, event)delivers to local sockets immediately, then broadcasts aBackplaneEnvelopeso every other pod re-resolves the target against its own registry and delivers to its sockets (the origin pod skips its own echo). This makes the samepublishcall reach a socket on any replica — required to run the WS service with >1 pod, and the cross-pod path for non-AI publishers. Selected at runtime viaSMOOTH_AGENT_BACKPLANE(memory|redis/valkey|nats) +SMOOTH_AGENT_BACKPLANE_URL; default stays single-process in-memory.Targetis nowSerialize/Deserializeand a sharedBackplaneEnvelopeis exposed so a host's own transport adapter can speak the same wire format. New crates:adapters/backplane-redis,adapters/backplane-nats(cross-pod fan-out proven end-to-end over real Redis + NATS via testcontainers).