Repository navigation
changeset: release the org-scoping fix + turn cost / tool-span OTel work - #472
Merged
Merged
Conversation
…el work #470 and #471 both merged without a changeset, so nothing would publish and neither fix would reach any consumer — the crates.io release here is changeset-driven. This releases both. The org-scoping half is the urgent one: until the published crate moves, chat-ws and copilot-ws keep scoping every tenant's host tools and persona to reference-org in production. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LkCz96UfUxcai5RU4LwPnG
🦋 Changeset detectedLatest commit: 7404464 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
#470 and #471 both merged without a changeset. The crates.io release in this repo is changeset-driven, so as things stand neither fix publishes and neither reaches a consumer — they sit on
mainlooking done.That is the failure mode worth naming: a merged fix and a shipped fix are different things here, and nothing in CI distinguishes them.
Why the org-scoping half is urgent
Until the published crate moves,
chat-wsandcopilot-wsin the monorepo keep building against the old pin, so production continues to scope every tenant's host tools and persona toreference-org— for every customer, on every turn.Contents
handle_send_messageboundorg_idtwice, the second binding shadowing the first withSEED_ORG_ID. The gateway key came from the first binding, so per-org billing stayed correct and hid the split.TurnUsage.cost_usd, but never recorded, so every consumer read "cost not measured"); tool spans now carrygen_ai.system/gen_ai.operation.name/gen_ai.conversation.id/smooai.org_id, without which OTLP consumers gating ongen_ai.systemdiscarded every tool span ever emitted.A gateway cost of
0is deliberately not recorded as a cost — it means the model is unpriced, not free, and writing it as real would silently under-bill.After this merges
The bot's version PR publishes the crates; then the monorepo pin bump (
rust/chat-ws,rust/copilot-ws) and an image rebuild carry it to prod. I'm driving that.🤖 Generated with Claude Code
https://claude.ai/code/session_01LkCz96UfUxcai5RU4LwPnG