What evloghq/evlog shipped
Written by FoxPlug from the repository's own releases; not affiliated with Evlog. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/evloghq/evlog; Evlog did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- The fs drain now creates its log directories and files readable by the owner only on macOS and Linux, instead of following the process umask. Pull request #1002
- Added opt-in redaction built-ins that detect credentials by value under any key and inside longer strings. Pull request #999
- Five drain adapters now split batches at each provider's per-request limit instead of sending an oversized batch as one request and having it rejected. Pull request #1005
- Stack frame parsing now runs in linear time instead of quadratic time on adversarial input. Pull request #988
- Pretty output on Node now escapes control characters in field values so a crafted value cannot rewrite the lines printed to the terminal. Pull request #981
- The evlog logs command now escapes control characters before printing logged values to the terminal. Pull request #990
- Integration request loggers are now typed with a required fork, covering Hono, Express, NestJS, Elysia, React Router and oRPC. Pull request #1011
- DefineEvlogHook now reads the v27 session events of eve 0.84 and later alongside the v26 events it already handled. Pull request #1019
- The Nuxt module now registers the Nitro v3 error handler and plugin when it detects Nitro 3, keeping error response status codes and JSON content type. Pull request #1007
- Six drains now trim trailing slashes from endpoints without a regex. Pull request #991
Why it matters
This week tightens the parts of the project that handle data leaving the process: log files are no longer world-readable, batches respect provider limits, and terminal output escapes control characters. Redaction can now catch credentials by their value rather than only by key name, which covers keys users did not think to list. Integration request loggers also get a stricter type for fork, so code that relies on forking the request logger is checked.
Changelog entry
- The fs drain creates directories and files readable by the owner only on macOS and Linux. Pull request #1002
- Add opt-in redaction built-ins that detect credentials by value under any key. Pull request #999
- Split adapter batches at each provider's per-request limits across five drains. Pull request #1005
- Parse stack frames in linear time. Pull request #988
- Escape control characters in pretty output on Node. Pull request #981
- Escape control characters in evlog logs output. Pull request #990
- Type log.fork() as required on integration request loggers. Pull request #1011
- Read the v27 session events of eve 0.84 and later in defineEvlogHook. Pull request #1019
- Register the Nitro v3 error handler and plugin on Nitro 3 in the Nuxt module. Pull request #1007
- Trim trailing slashes in drain endpoints without a regex. Pull request #991
- Attach the no-op logger on requests evlog does not log. Pull request #1015
- Read Vue script blocks closed with whitespace before the closing bracket in evlog map. Pull request #992
Evlog this week: log files from the fs drain are now owner-only, five drain adapters split batches at provider limits, and redaction can detect credentials by value under any key. Terminal output now escapes control characters, and stack frame parsing is linear.
This week in Evlog: the fs drain now creates log directories and files readable by the owner only. Five drain adapters split batches at each provider's per-request limit instead of sending one oversized request. Redaction gained opt-in built-ins that detect credentials by value, under any key and inside longer strings. Pretty output and the evlog logs command escape control characters, stack frame parsing runs in linear time, and integration request loggers are typed with a required fork across Hono, Express, NestJS, Elysia, React Router and oRPC.
Week of October 12, 2026
What shipped
- Released evlog 2.33.1 with a SvelteKit 3 handleError fix and bearer token redaction that now runs before every other built-in. Release
- Shipped evlog 3.0.0-beta.0, which requires Node.js 22 or later and carries a logged error's HTTP status in status only. Release
- Added evlog/effect, an Effect 4 integration that gives every HttpRouter and HttpApi request one wide event and turns jobs, queue messages and Durable Object alarms into events. Pull request #855
- Added the evlog/sazabi drain adapter, which sends wide events to a Sazabi log stream over OTLP/HTTP. Pull request #852
- Released @evlog/cli 0.11.0, where evlog init offers Grafana Loki, ClickHouse and Sazabi as production destinations. Release
- Added an opt-in issues option to the Sentry drain so error wide events can be sent as Sentry issues. Pull request #856
- Fixed three core bugs: a cycle in the logger context overflowing the stack, non-plain objects being merged, and IBAN masking running after card masking. Pull request #907
- Made built-in email and jwt redaction linear instead of quadratic, so long client-controlled strings no longer slow down redaction. Pull request #867
- Improved the speed of set(), emit and default redaction in core. Pull request #905
- Released evlog 2.33.0 with the Effect 4 integration in beta, Loki and ClickHouse in evlog init, and Sazabi listed across the docs. Release
Why it matters
This week brings an Effect 4 integration, a Sazabi drain adapter and new destinations in evlog init, so more setups can send wide events where they already keep their logs. It also ships 3.0.0-beta.0, which requires Node.js 22 or later and changes how a logged error carries its HTTP status, alongside fixes to redaction, core errors and the Sentry drain.
Changelog entry
- Evlog 2.33.1: fix SvelteKit 3 handleError input and run bearer redaction before other built-ins. Release
- Evlog 3.0.0-beta.0: require Node.js 22 or later; a logged error carries its HTTP status in status only. Release
- Add evlog/effect, an Effect 4 integration for HttpRouter and HttpApi requests, jobs, queue messages and Durable Object alarms. Pull request #855
- Add the evlog/sazabi drain adapter, sending wide events to a Sazabi log stream over OTLP/HTTP. Pull request #852
- @evlog/cli 0.11.0: evlog init offers Grafana Loki, ClickHouse and Sazabi as production destinations. Release
- Sentry drain: add an opt-in issues option to send error wide events as Sentry issues. Pull request #856
- Core: cut cycles in the logger context, merge only plain objects, and mask IBAN before cards. Pull request #907
- Core: built-in email and jwt redaction now run in linear time. Pull request #867
- Core: speed up set(), emit and default redaction. Pull request #905
- Core: retry 408 responses in HTTP drains instead of dropping the batch. Pull request #893
- Nuxt: answer 403 to a null or malformed origin on the client ingest endpoint. Pull request #890
- Core: accept only exact loopback origins and hosts on the stream server. Pull request #889
Evlog 2.33.1 and 3.0.0-beta.0 are out: SvelteKit 3 handleError support, bearer redaction running first, an Effect 4 integration, a Sazabi drain, and Loki and ClickHouse in evlog init.
This week Evlog shipped 2.33.1 and 3.0.0-beta.0. The 2.33.1 release fixes SvelteKit 3's handleError input and runs bearer redaction before every other built-in. The 3.0.0 beta requires Node.js 22 or later and carries a logged error's HTTP status in status only. Also new: an Effect 4 integration that gives every HttpRouter and HttpApi request one wide event, a Sazabi drain over OTLP/HTTP, and Grafana Loki, ClickHouse and Sazabi offered as production destinations in evlog init. On the core side, email and jwt redaction are now linear, the Sentry drain can send error wide events as issues, and several bugs found while benchmarking are fixed.
Week of September 28, 2026
What shipped
- Evlog@2.30.0 released with Vercel integration rebuild on scoped MCP connection, native file memory in eve, and git checkout support for cloning repositories. Release
- @evlog/cli@0.8.0 adds GitHub Actions output format and framework support for Express and Fastify with a plugin layout. Release
- @evlog/cli@0.7.0 ships the evlog executable so npx evlog init, map, doctor and agents work without installation setup. Release
- @evlog/signals added as typed model judgments on wide events with confidence scores stored under event.signals. Pull request #764
- Evlog map --format github outputs workflow commands for GitHub Actions to render findings on pull request diffs. Pull request #767
- Framework support refactored into one directory per framework with detection, labels, docs and accessor logic colocated. Pull request #766
- Evlog map --json now carries grade field (excellent/good/needs-work/poor) and --baseline-label flag for consistent scoring. Pull request #773
- Docs now use framework picker to show per-framework snippets with choice persisted in cookies across code blocks. Pull request #768
- OTLP exporter aligned with OpenTelemetry spec reading standardized environment variables for endpoint, headers and resource attributes. Pull request #748
- Error causes in wide events now serialize name, message, stack and metadata, with circular references marked. Pull request #738
Why it matters
The evlog executable ships by default, making the CLI accessible without setup. GitHub Actions integration lets findings appear directly on pull request diffs. Framework support is now plugin-based and extensible, with docs updated to match the reader's framework choice.
Changelog entry
- Evlog@2.30.0: Vercel integration rebuild, native file memory, git checkout support Release
- @evlog/cli@0.8.0: GitHub Actions format, Express and Fastify support Release
- @evlog/cli@0.7.0: Executable ships with evlog package Release
- @evlog/signals@0.2.0: Typed model judgments on events Pull request #764
- Evlog map --json includes grade field and --baseline-label flag Pull request #773
- Evlog map --format github outputs workflow commands for pull request diffs Pull request #767
- Framework support refactored with one directory per framework Pull request #766
- Docs framework picker persists choice across code blocks Pull request #768
- OTLP exporter reads OpenTelemetry standard environment variables Pull request #748
- Caller span recorded as parentSpanId, improves log-to-span correlation Pull request #749
- Error causes serialize with name, message, stack and metadata Pull request #738
- @evlog/telemetry@0.3.3: Refactoring from executable work Release
Evlog@2.30.0: executable ships by default, map --json carries grades, GitHub Actions format renders findings on PR diffs, Express and Fastify frameworks supported.
Evlog@2.30.0 is out. The CLI executable ships by default—no setup needed. GitHub Actions integration renders findings on pull request diffs. Map command now outputs grades and supports GitHub workflow format. Framework support refactored into plugins; docs show per-framework snippets based on your choice.
Week of September 14, 2026
What shipped
- Evi can now work on repositories that use evlog, not just evlog itself, by carrying three published skills for log analysis and patterns. Pull request #726
- Technical replies on GitHub now include collapsed ELI5 explanations for clarity, while Slack stays conversational. Pull request #727
- Evi repository configuration is now centralized in one module, defaulting to evloghq/evlog but readable from environment and channel state. Pull request #722
- Upgraded eve dependency to 0.63.0 to match the eve-extension version requirement. Pull request #718
Why it matters
Evi can now work across repositories using evlog and access their code directly in the sandbox. The centralized repository configuration makes Evi more flexible for different deployment contexts. These changes expand Evi's utility beyond analyzing evlog itself.
Changelog entry
- Evi can now work on repositories using evlog with three published skills for log analysis and pattern review Pull request #726
- Technical replies on GitHub now include optional collapsed ELI5 explanations Pull request #727
- Centralized repository resolution via EVI_REPOSITORY environment variable and channel state Pull request #722
- Upgraded eve to 0.63.0 Pull request #718
Evi now works on any repository using evlog, not just evlog itself. Clone code directly into the sandbox and apply logging patterns across your projects.
This week Evi expanded beyond analyzing evlog to work on any repository that uses it. You can now carry published logging skills into new projects, clone repositories directly into the sandbox, and centralize repository configuration. Technical replies gain collapsible explanations for clarity.