chore(repo): version packages#386
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
evlog@2.19.2
Patch Changes
#384
6eb0957Thanks @nadaniels! - fix(hono): resolve "ReadableStream is locked" error with AI SDK streaming responsesUsing
createUIMessageStreamResponseorcreateAgentUIStreamResponsefrom the Vercel AI SDK inside a Hono route would throwERR_INVALID_STATE: ReadableStream is lockedwhen running under@hono/node-server.Root cause: The middleware called
createObservedBody(c.res.body)(which callsbody.getReader(), locking the stream) and then relied on Hono'scomposeto updatec.reswith the wrapped response via the middleware return value. However, Hono skips that update whencontext.finalizedis alreadytrue— which is always the case after a route handler returns aResponse. This leftc.respointing at the original response whose body was now locked, so@hono/node-server's subsequentresponse.body.getReader()call threw.Fix: Explicitly assign
c.res = await finishResponse(c.res, ...)instead of returning the wrapped response, soc.resis always updated regardless ofcontext.finalized.Closes #382
evlog-community-adapter-skeleton@5.0.2
Patch Changes
6eb0957]:evlog-community-enricher-skeleton@5.0.2
Patch Changes
6eb0957]:evlog-community-framework-skeleton@5.0.2
Patch Changes
6eb0957]: