π¦ New version release - #480
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.53.1
Patch Changes
e0077e4: Stop exporting fabricated token counts on the turn span, and adopt the cross-language
cost_unavailableattribute.gen_ai.usage.input_tokenswas published whenever either count was non-zero. That||was the whole bug: when the gateway drops the usage chunk,smooai-smooth-operator-core'scollect_streamfabricates the struct βprompt_tokenshardcoded to0andcompletion_tokensestimated ascontent.len() / 4β so the fabricated struct always had a non-zero completion count, and the||publishedinput_tokens = 0beside it. LiteLLM drops that chunk forsmooth-*aliases, so this was the common path, not an edge case: no streamed turn has ever exported a measured token count.The estimated output count looked plausible precisely because it is derived from the reply text β an estimate computed from the output cannot help but track the output. Only the zeroed input half looked obviously wrong.
Now gated on
prompt_tokens > 0alone: both counts are exported, or neither. Absent is honest;0is a lie. The underlying fabrication still needs fixing in core.Also adds
smooai.gen_ai.cost_unavailable = "unpriced", set instead ofgen_ai.usage.cost_usdwhen no cost could be established β the same attribute name and value the TypeScript emitters use, so a consumer never has to special-case per engine.@smooai/smooth-operator-web-chat-example@0.0.93
Patch Changes