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

Releases

evlog@2.33.1

Patch Changes

• #906 da6ef1a Thanks @HugoRCD! - The bearer redaction built-in now runs before every other built-in, so a Bearer token is masked whole. A token shaped like an IBAN or a card number was partly rewritten first and then no longer matched: Bearer FR76ABCD123456789012 was logged as Bearer FR76****012, and Bearer 4111111111111111 as Bearer ****1111. Both are now Bearer ***, and so is a JWT after Bearer, which was logged as Bearer eyJ***.***.

• #906 da6ef1a Thanks @HugoRCD! - The iban redaction built-in masks a spaced IBAN whole when creditCard is also on, as it is with the default redact: true. The card pattern ran first and matched the digits inside it, so FR76 3000 6000 0112 3456 7890 189 was logged as FR76 ****3456 7890 189. It is now FR76****189. A builtins list runs in a fixed order, whatever order it is written in.

• #906 da6ef1a Thanks @HugoRCD! - A cycle in the context passed to createLogger() or createRequestLogger(), or in the fields passed to emit(), is logged as '[Circular]', as it already was for set(). It used to overflow the stack when redaction was on, which it is by default in production. An Error in that context or in emit() fields is now serialized with its name, message and stack instead of being logged as {}.

• #906 da6ef1a Thanks @HugoRCD! - log.set() only merges plain objects. A class instance or a Date is now a value: the next set() on the same key replaces it. Before, merging into one wrote the new fields into the caller's own object, and a second Date on the same key was ignored. log.set({ account }) followed by log.set({ account: { plan: 'pro' } }) now logs { plan: 'pro' } and leaves account untouched.

• #913 3f1617d Thanks @HugoRCD! - createEvlogHooks().handleError and evlogHandleError() now accept SvelteKit 3's handleError input (kind, error, event) and type-check as Kit 3's HandleServerError. On SvelteKit 3, errors that are not an EvlogError keep Kit's own status and message instead of being overwritten with undefined, which made production responses return HTTP 200. The hook no longer reads Kit 3's deprecated status and message input properties, so dev mode stops logging deprecation warnings. SvelteKit 2 behavior is unchanged.

[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 8:03pm UTC
evlog-docs	Ignored	Preview	Oct 17, 2026 8:03pm UTC
evlog-render-lab	Ignored	Preview	Oct 17, 2026 8:03pm UTC
evlog-telemetry	Ignored	Preview	Oct 17, 2026 8:03pm UTC
just-use-evlog	Ignored	Preview	Oct 17, 2026 8:03pm 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: b2fdd318-fec4-45ac-9da9-fce8fdc9289c

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.}