Skip to content

chore(repo): version packages - #635

Merged
HugoRCD merged 1 commit into
mainfrom
changeset-release/main
Aug 31, 2026
Merged

chore(repo): version packages#635
HugoRCD merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

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 ada6408 Thanks @HugoRCD! - createError({ data }) returns an extra payload to the client, merged into the response body's data object next to code, why, fix, and link. Those four win on a key collision, and anything the client must never see still goes in internal. Read it client-side with parseError(err).data.

    The Nitro and Nuxt error handler no longer drops data from errors thrown with h3's createError. It now follows Nitro's own rule for what it withholds: the message and data of an unhandled error are hidden in production, while a deliberate createError({ status: 500, message }) keeps both. Development returns the error as thrown, as Nitro does.

Patch Changes

  • c0a0385 Thanks @HugoRCD! - useLogger() from evlog/eve no 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 c2af424 Thanks @HugoRCD! - evlog/hono records errors again in apps that register app.onError. Hono hands a thrown error to onError at 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 no error field. The wide event now carries the error and the status the handler actually returned.

@evlog/cli@0.6.1

Patch Changes

@vercel

vercel Bot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
evi Ready Ready Preview Aug 31, 2026 10:21am
evlog-docs Ready Ready Preview, v0 Aug 31, 2026 10:21am
evlog-render-lab Ready Ready Preview Aug 31, 2026 10:21am
evlog-telemetry Ready Ready Preview Aug 31, 2026 10:21am
just-use-evlog Ready Ready Preview Aug 31, 2026 10:21am

Request Review

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from fb4a413 to 692c2dd Compare August 27, 2026 19:14
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 692c2dd to 9d5ac42 Compare August 27, 2026 20:41
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 9d5ac42 to 981818a Compare August 27, 2026 20:53
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 981818a to a4fe238 Compare August 27, 2026 21:15
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from eeb9f8e to db3f6e5 Compare August 28, 2026 15:49
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from db3f6e5 to f9a62c1 Compare August 28, 2026 16:47
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from f9a62c1 to 8c4b34b Compare August 28, 2026 19:43
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 8c4b34b to 4b77b9e Compare August 29, 2026 11:42
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 4b77b9e to ed33b04 Compare August 29, 2026 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant