[github-actions]

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 v3, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

v3 is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on v3.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

evlog@3.0.0-beta.0

Major Changes

• #894 24ca3e3 Thanks @evlogai! - A logged error carries its HTTP status in status only. The statusCode, statusText and statusMessage fields are no longer written into the wide event or the log, on the server or in the browser, so a drain or a query that read them needs to read status. The message that statusText and statusMessage repeated is already logged as message.

  An h3 or Nuxt error keeps its own statusCode as input: the logger reads it and logs it as status.

  The logged error, trimmed to the fields that changed:

  {
    "name": "EvlogError",
    "message": "Payment could not be completed",
    "status": 402,
    "data": { "why": "Card declined" }
  }

  Before this change the same error also logged statusCode: 402, statusText and statusMessage.

  A toJSON that leaves a field out now also keeps that field out after a second set() on the same key, so a field hidden by toJSON is no longer logged through that path.

• #861 32ded2c Thanks @evlogai! - Require Node.js 22 or later. engines.node is now >=22.0.0 (it was >=18.0.0, and >=20.0.0 for @evlog/signals). The build target follows the floor, so the published output targets Node 22.

  Nuxt 4.6.1 declares ^22.22.3 || ^24.15.0 || >=26.0.0, so Nuxt projects should run one of those ranges.

Patch Changes

• #880 a0187db Thanks @evlogai! - The Sentry drain's issues option reads an error's status, then the event's status, when it decides whether an event is a 4xx. It no longer reads the legacy statusCode, so an error that only carries statusCode is classified by the event's status. Logs and the drained wide event are unchanged.

• #860 0baa9e8 Thanks @evlogai! - The published packages no longer ship .map files. They pointed to src/, which is not part of the package, so they only added to the install size. evlog drops from 330 files (about 2.0 MB unpacked) to 178 files (about 865 KB). No runtime or API change.

@evlog/nuxthub@3.0.0-beta.0

Major Changes

• #861 32ded2c Thanks @evlogai! - Require Node.js 22 or later. engines.node is now >=22.0.0 (it was >=18.0.0, and >=20.0.0 for @evlog/signals). The build target follows the floor, so the published output targets Node 22.

  Nuxt 4.6.1 declares ^22.22.3 || ^24.15.0 || >=26.0.0, so Nuxt projects should run one of those ranges.

Patch Changes

• Updated dependencies [24ca3e3, 32ded2c, a0187db, 0baa9e8]:
  • evlog@3.0.0-beta.0

@evlog/signals@1.0.0-beta.0

Major Changes

• #861 32ded2c Thanks @evlogai! - Require Node.js 22 or later. engines.node is now >=22.0.0 (it was >=18.0.0, and >=20.0.0 for @evlog/signals). The build target follows the floor, so the published output targets Node 22.

  Nuxt 4.6.1 declares ^22.22.3 || ^24.15.0 || >=26.0.0, so Nuxt projects should run one of those ranges.

Patch Changes

• #860 0baa9e8 Thanks @evlogai! - The published packages no longer ship .map files. They pointed to src/, which is not part of the package, so they only added to the install size. evlog drops from 330 files (about 2.0 MB unpacked) to 178 files (about 865 KB). No runtime or API change.

• Updated dependencies [24ca3e3, 32ded2c, a0187db, 0baa9e8]:

  • evlog@3.0.0-beta.0

@evlog/telemetry@1.0.0-beta.0

Major Changes

• #861 32ded2c Thanks @evlogai! - Require Node.js 22 or later. engines.node is now >=22.0.0 (it was >=18.0.0, and >=20.0.0 for @evlog/signals). The build target follows the floor, so the published output targets Node 22.

  Nuxt 4.6.1 declares ^22.22.3 || ^24.15.0 || >=26.0.0, so Nuxt projects should run one of those ranges.

Patch Changes

• #860 0baa9e8 Thanks @evlogai! - The published packages no longer ship .map files. They pointed to src/, which is not part of the package, so they only added to the install size. evlog drops from 330 files (about 2.0 MB unpacked) to 178 files (about 865 KB). No runtime or API change.

@evlog/cli@1.0.0-beta.0

Patch Changes

• #860 0baa9e8 Thanks @evlogai! - The published packages no longer ship .map files. They pointed to src/, which is not part of the package, so they only added to the install size. evlog drops from 330 files (about 2.0 MB unpacked) to 178 files (about 865 KB). No runtime or API change.

• Updated dependencies [24ca3e3, 32ded2c, a0187db, 0baa9e8]:

  • evlog@3.0.0-beta.0
  • @evlog/telemetry@1.0.0-beta.0

[vercel]

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

5 Skipped Deployments

Project	Deployment	Actions	Updated
evi	Ignored	Preview	Oct 17, 2026 3:20pm UTC
evlog-docs	Ignored	Preview	Oct 17, 2026 3:20pm UTC
evlog-render-lab	Ignored	Preview	Oct 17, 2026 3:20pm UTC
evlog-telemetry	Ignored	Preview	Oct 17, 2026 3:20pm UTC
just-use-evlog	Ignored	Preview	Oct 17, 2026 3:20pm UTC

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 74dcebcb-f463-4059-a9c8-6f52d219cd5f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}