Open
Conversation
ee36253 to
f1baa7c
Compare
f1baa7c to
10fd398
Compare
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
agents@0.6.1
Patch Changes
#1003
d24936cThanks @threepointone! - Fix:throw new Error()in AgentWorkflow now triggersonWorkflowErroron the AgentPreviously, throwing an error inside a workflow's
run()method would halt the workflow but never notify the Agent viaonWorkflowError. Only explicitstep.reportError()calls triggered the callback, but those did not halt the workflow.Now, unhandled errors in
run()are automatically caught and reported to the Agent before re-throwing. A double-notification guard (_errorReportedflag) ensures that ifstep.reportError()was already called before the throw, the auto-report is skipped.#997
a570ea5Thanks @threepointone! - Security hardening for Agent and MCP subsystems:consumeStatewarning logs to prevent sensitive data leakagesendIdentityOnConnect(defaulttruewill change tofalsein next major) and CORSAuthorizationheader with wildcard origin (will be removed from defaults in next major)#992
4fcf179Thanks @Muhammad-Bin-Ali! - Fix email routing to handle lowercased agent names from email infrastructureEmail servers normalize addresses to lowercase, so
SomeAgent+id@domain.comarrives assomeagent+id@domain.com. The router now registers a lowercase key in addition to the original binding name and kebab-case version, so all three forms resolve correctly.@cloudflare/ai-chat@0.1.6
Patch Changes
#989
8404954Thanks @threepointone! - Fix active streams losing UI state after reconnect and dead streams after DO hibernation.replayCompletesignal after replaying stored chunks for live streams, so the client flushes accumulated parts to React state immediately instead of waiting for the next live chunk._isLiveflag onResumableStream. On reconnect, senddone: true, complete the stream, and reconstruct/persist the partial assistant message from stored chunks.activeStreamRefonreplayComplete(keeps stream alive for subsequent live chunks) and ondoneduring replay (finalizes orphaned streams).#993
f706e3fThanks @ferdousbhai! - fix(ai-chat): preserve server tool outputs when client sends approval-responded state_mergeIncomingWithServerStatenow treatsapproval-respondedthe same asinput-availablewhen the server already hasoutput-availablefor a tool call,preventing stale client state from overwriting completed tool results.