chore(deps): update dependency xsschema to ^0.5.1 - #175
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
✅ Deploy Preview for neuri ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
renovate
Bot
force-pushed
the
renovate/xsschema-0.x
branch
from
February 16, 2026 18:20
a7d7cb9 to
13096ba
Compare
renovate
Bot
force-pushed
the
renovate/xsschema-0.x
branch
from
March 13, 2026 10:16
13096ba to
981819e
Compare
renovate
Bot
force-pushed
the
renovate/xsschema-0.x
branch
from
May 12, 2026 11:57
981819e to
9eed023
Compare
renovate
Bot
force-pushed
the
renovate/xsschema-0.x
branch
2 times, most recently
from
August 29, 2026 17:52
13d361d to
090dad6
Compare
renovate
Bot
force-pushed
the
renovate/xsschema-0.x
branch
from
October 1, 2026 04:30
090dad6 to
f3cb3ff
Compare
This branch has not been deployed
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 contains the following updates:
^0.4.2→^0.5.1Release Notes
moeru-ai/xsai (xsschema)
v0.5.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.5.0: "mirai"Compare Source
🧳 Migration Guides
Version 0.5.0 includes breaking API changes. Upgrade all xsAI packages to 0.5.0 together and avoid mixing 0.4.x and 0.5.x packages.
Replace
maxStepswithstopWhenReplace:
with:
The default remains one step.
CompletionStep.stepTypehas been removed; usefinishReason,toolCalls, andstepsinstead.stopWhenis evaluated before tool execution. With the defaultstepCountAtLeast(1),generateText()returns pendingtoolCallsfor manual execution andtoolResultsmay be empty. If your 0.4.4 code relied on automatic tool execution, setstopWhen: stepCountAtLeast(2)or use a custom condition that allows another step. If you need manual approval, keep the default behavior, execute or approve the returnedtoolCalls, append the resulting tool messages tomessages, and callgenerateText()again. Top-level tool results describe the final step; results from earlier steps are available insteps[n].toolResults.Update stream event handling
streamText().eventStreamnow provides normalized xsAI events.fullStreamnow provides raw provider chat-completion chunks.Common event changes:
text-deltawithtexttext.deltawithdeltareasoning-deltawithtextreasoning.deltawithdeltatool-call-streaming-starttool-call.starttool-call-deltawithargsTextDeltatool-call.deltawithdeltatool-calltool-call.donetool-resulttool-result.donefinishstep.doneUpdate
onEventhandlers accordingly. The same changes apply tostreamObject.Update usage fields
Normalized usage fields now use camelCase:
generateText()andgenerateObject()now also returntotalUsage, which includes usage from all steps and tool-call follow-ups.Update tool integrations
If you use
executeTool()directly, its return field has changed frommessagetoresult.Version 0.5.0 also adds tool input validation,
preToolCall, andpostToolCall.defineTool()is the recommended synchronous API for schemas that support Standard JSON Schema.Tool parsing and execution failures are generally returned as tool results with
isError: true.Update error handling
Errors are now represented by dedicated classes such as
APICallError,InvalidResponseError,JSONParseError,InvalidToolCallError,InvalidToolInputError, andToolExecutionError.If your code checks
XSAIErrorfields directly, update it to use the specialized error classes or the errorcodeproperty.Removed and deprecated APIs
toAsyncIteratorhas been removed from@xsai/utils-stream.extractReasoning()andextractReasoningStream()are deprecated. UsegenerateText().reasoningTextandstreamText().reasoningTextStreaminstead.For speech streaming, use the new
@xsai/stream-speechpackage and itsstreamSpeech()API.🚨 Breaking Changes
🚀 Features
🐞 Bug Fixes
🏎 Performance
shared-streampackage - by @kwaa in #283 (b2790)View changes on GitHub
v0.4.4Compare Source
🐞 Bug Fixes
executeonly - by @Wyatex in #270 (02092)View changes on GitHub
v0.4.3Compare Source
🏎 Performance
Promise.allfor tool calling - by @dsh0416 in #264 (9241e)View changes on GitHub
Configuration
📅 Schedule: (in timezone UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.