π¦ New version release - #473
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.52.3
Patch Changes
aa9af9e: Fix multi-tenant org scoping in
handle_send_message, and make LLM turn spans carry cost and tool spans self-identifying.Org scoping (handle_send_message: stop re-binding the turn's org to the seed orgΒ #470).
handle_send_messageboundorg_idtwice: once correctly from the conversation (used to resolve the per-org gateway key) and again ~120 lines later asSEED_ORG_ID, shadowing it. Everything downstream of the second binding β the org persona override and the host tool provider's scope β sawreference-orgon a multi-tenant host, for every tenant. Because the gateway key came from the first binding, per-org billing and per-org LLM keys stayed correct, which is why the split went unnoticed. Now reuses the derived org and falls back to the seed org only when it is empty, so the single-org reference/local flavor is unchanged.Turn cost (otel: record per-turn cost, and make tool spans self-identifyingΒ #471). The gateway's authoritative per-response cost was already parsed by
smooai-smooth-operator-coreand carried toTurnUsage.cost_usd, but nothing recorded it on the span, sogen_ai.usage.cost_usdwas never emitted and consumers showed "cost not measured". The turn span now records it. A non-positive or non-finite value is dropped rather than written as0β a gateway0means the model is unpriced, not free, and recording it as a real cost would silently under-bill.Self-identifying tool spans (otel: record per-turn cost, and make tool spans self-identifyingΒ #471). Tool spans carried neither
gen_ai.systemnorgen_ai.operation.name, and OTLP consumers that gate ongen_ai.systemtherefore discarded every tool span ever emitted. They now carrygen_ai.system,gen_ai.operation.name,gen_ai.conversation.idandsmooai.org_id, so a tool span is both ingestable and joinable to its conversation. Fixed at both emission sites βrunner::run_streaming_turnandKnowledgeChatRuntime::run_turnβ which had the identical gap.@smooai/smooth-operator-web-chat-example@0.0.91
Patch Changes