🦋 New version release - #507
Merged
Merged
Conversation
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
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@1.56.0
Minor Changes
0f9e90f: Fix silently-dropped protocol frames in the Go, Python, .NET and TypeScript clients, and add the
submit_interactionverb to Go/Python/.NET.The generated wire types for
stream_preamble,stream_reasoning,interaction_requiredandinteraction_invalidexisted in every language, but the hand-maintained dispatch unions were never updated. Every one of those frames was rejected by each client's own frame guard and then discarded by its dispatch loop — Go'sParseServerEventreturnedUnknownEventErrorand the read loopcontinued, Python'sparse_eventraised and_handle_frameswallowed it, and .NET'sServerEventConverterthrew aJsonExceptionthe client caught and dropped.Impact: a session declaring a Rich Interaction (
identity_form,choice_chips) parked a turn that Go/Python/.NET consumers never saw — the turn hung to the turn timeout (and forever on .NET, which has none).stream_preambleandstream_reasoningare emitted by the production server today, so preamble and reasoning tokens were being discarded by all four clients, TypeScript included.As*accessors,ActionSubmitInteraction, andClient.SubmitInteraction.EventTypeand theServerEventunion,submit_interactiontoActionTypeandClientAction,SmoothAgentClient.submit_interaction, and the missing entries invalidate.py's schema maps.StreamPreambleEvent,StreamReasoningEvent,InteractionRequiredEvent,InteractionInvalidEvent, wired them intoServerEventConverterandEventTypes.All, and addedSubmitInteractionAction+SmoothAgentClient.SubmitInteractionAsync.stream_reasoningtoEVENT_TYPES/ServerEventand tovalidate.ts's event→schema map. (The shipped web-chat example already had acase 'stream_reasoning'that could never fire.)Each language also gains a drift guard that derives the expected discriminator set from
spec/events/*.schema.jsonandspec/actions/*.schema.jsonat test time, so a future event schema that isn't wired into a dispatch union fails the build instead of being dropped at runtime.@smooai/smooth-operator-web-chat-example@0.0.102
Patch Changes