🦋 New version release - #355
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
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.
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.40.0
Minor Changes
15dab99: Release the .NET server work that has been sitting on
mainunpublished: the file-transfer contract (file transfer (dotnet): parse images/files, wire directive sink to Rust parity #348) and server-side skill resolution (skill resolution (dotnet): resolve send_message.skill server-side (#338 parity) #352).Neither shipped, and the cause was a changeset-target slip rather than anything wrong with the code.
@smooai/smooth-operator-serveris the TypeScript server npm package; the .NET NuGetSmooAI.SmoothOperator.Servertakes its<Version>fromscripts/sync-versions.mjs, which stamps the lockstep anchor@smooai/smooth-operator(typescript/package.json) onto every non-npm manifest. file transfer (dotnet): parse images/files, wire directive sink to Rust parity #348's changeset named only@smooai/smooth-operator-server, so release 🦋 New version release #349 bumped the TS package to 1.8.0 and left the anchor at 1.39.0 — and the .NET package was never republished. The sibling TS PR file transfer (ts): parse images/files, wire directive sink to Rust parity #346 got this right, naming both packages.Net effect for consumers:
SmooAI.SmoothOperator.Server1.39.0 has noTurnContext, no directive sink, and noimages[]/files[]ingest, even thoughmainhas had all of it since 2026-08-11. Bumping the anchor stamps the csproj and publishes the NuGet, so 1.39.0 consumers get file transfer and skill resolution in one release.No source change — this is purely the release plumbing the two .NET PRs missed.
@smooai/smooth-operator-web-chat-example@0.0.52
Patch Changes