chore(repo): version packages - #635
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 27, 2026 19:14
fb4a413 to
692c2dd
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 27, 2026 20:41
692c2dd to
9d5ac42
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 27, 2026 20:53
9d5ac42 to
981818a
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 27, 2026 21:15
981818a to
a4fe238
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 28, 2026 15:49
eeb9f8e to
db3f6e5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 28, 2026 16:47
db3f6e5 to
f9a62c1
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 28, 2026 19:43
f9a62c1 to
8c4b34b
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 29, 2026 11:42
8c4b34b to
4b77b9e
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 29, 2026 13:12
4b77b9e to
ed33b04
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
evlog@2.28.0
Minor Changes
#643
ada6408Thanks @HugoRCD! -createError({ data })returns an extra payload to the client, merged into the response body'sdataobject next tocode,why,fix, andlink. Those four win on a key collision, and anything the client must never see still goes ininternal. Read it client-side withparseError(err).data.The Nitro and Nuxt error handler no longer drops
datafrom errors thrown with h3'screateError. It now follows Nitro's own rule for what it withholds: the message anddataof an unhandled error are hidden in production, while a deliberatecreateError({ status: 500, message })keeps both. Development returns the error as thrown, as Nitro does.Patch Changes
c0a0385Thanks @HugoRCD! -useLogger()fromevlog/eveno longer throws when it cannot reach the current turn's logger. It warns once for that turn and returns a logger that accepts every call and emits nothing, so a tool is never failed by its own instrumentation.Turn state is held per process, while an eve turn is durable and can resume in another process after a step boundary. A tool calling
useLogger(ctx)after such a resume used to throw, which failed the tool itself — a long-running turn could lose real work to a missing log field. Enrichment for that turn is dropped instead, and the warning names the turn so the gap is visible.#644
c2af424Thanks @HugoRCD! -evlog/honorecords errors again in apps that registerapp.onError. Hono hands a thrown error toonErrorat the route's own dispatch level, so the middleware resumed as if the request had succeeded and the failure was emitted as an info event with noerrorfield. The wide event now carries the error and the status the handler actually returned.@evlog/cli@0.6.1
Patch Changes
ada6408,c0a0385,c2af424]: