π¦ New version release - #312
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.36.3
Patch Changes
d17fa66: SECURITY: TS server β owner-check only conversations that HAVE an owner (Option B)
The per-user scoping rule shipped in SECURITY: TypeScript per-user conversation scoping (th-8fe998)Β #297 scoped an authenticated principal with no
emailclaim (and an anonymous connection to an auth-enabled server) to an unownablesentinel, and required
ownerEmail === scopeon every read. That denied such callersEVERYTHING β empty list, resume refused,
send_messagerefused β locking them out ofthe session they had just created, i.e. no anonymous or emailless chat at all on an
auth-enabled server. The identical rule in .NET hung CI on a WebSocket ACL test and was
reverted in Revert: .NET write-path scoping (#308) β hangs CI, denies anonymous/emailless principalsΒ #309; TS had no equivalent test, so it went unnoticed here.
mayReadnow allows a conversation with NO owner and owner-checks one that has anowner. The reported P0 stays closed: authenticated A still cannot read or write
authenticated B's owned session (
SESSION_NOT_FOUND, byte-identical to a never-existedid, nothing appended to B's log), and an emailless scope still matches no real owner β
the list stays empty for emailless principals rather than pooling every anonymous
visitor's chats into one readable bucket.
Owner comparison is now case-insensitive (read path and list selection), matching .NET
and Python β OIDC providers vary on the casing they emit for the same identity.
@smooai/smooth-operator-web-chat-example@0.0.39
Patch Changes