Repository navigation
chore(deps): update the pinned @evlog/cli to v0.12.0 - #10
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Observability score · 64needs work across 3 packages · unchanged against
Note No Fix first (4)
evlog map v0.12.0 · how the score works · what each check expects |
renovate
Bot
force-pushed
the
renovate/evlog-cli-0.x
branch
from
October 17, 2026 15:48
830932e to
26dea5b
Compare
renovate
Bot
force-pushed
the
renovate/evlog-cli-0.x
branch
from
October 30, 2026 08:21
26dea5b to
d10d627
Compare
renovate
Bot
force-pushed
the
renovate/evlog-cli-0.x
branch
from
November 7, 2026 15:16
d10d627 to
d31484c
Compare
renovate
Bot
force-pushed
the
renovate/evlog-cli-0.x
branch
from
November 20, 2026 18:37
d31484c to
ea173fe
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 contains the following updates:
0.8.0→0.12.0Release Notes
evloghq/evlog (@evlog/cli)
v0.12.0Compare Source
Minor Changes
8ee1a17Thanks @HugoRCD! -evlog mapnow records what each entry point's wide event carries. Every route inevlog.map.jsonand in--jsongains aneventkey with the dotted pathslog.set()writes (user.id,cart.items) and the literalactionof eachlog.audit()call. Comparing it between two scans shows which fields a change removes from your production logs. Routes that set nothing have noeventkey, and the existing keys are unchanged.Patch Changes
#1083
9621ea4Thanks @HugoRCD! -evlog agentsandevlog initno longer delete or duplicate text in anAGENTS.mdwhose evlog markers are not one clean pair. A file that lost<!-- evlog:end -->got a second block on one run and lost the section below it on the next. Both commands now stop withcli.AGENTS_MARKERS_UNPAIRED, exit 1 and leave the file as it is. A marker quoted in a sentence or a code fence is read as text.evlog initalso changes in four places:evlog/nitroorevlog/nitro/v3getsimport evlogalong withmodules: [evlog()]. It got the module entry with no import.errors.tsandaudit.tsparse when a service or a route starts with a digit (_3dShopErrors,_2FA_PASSWORD_CREATED) or a route holds a wildcard.npx skills addexits 1, and theAGENTS.mdblock no longer points at the skill that was not installed.evlog agentsalready did both.cli.WRITE_FAILED, which names the file and the ones written before it, under--jsontoo.evlog agentsdoes the same. Both printed a stack trace and left stdout empty.#1128
e1e33d0Thanks @HugoRCD! - Two fixes toevlog initandevlog agents.evlog init --apps apps/websets up the app. Workspace app paths were built with backslashes there, so the forward-slash form was rejected as unknown, and the JSONappvalues and the per-app headings carried backslashes. They use forward slashes on every platform, and--apps apps\webstill selects the app.npx skills addfails, the reported error is the last line it wrote before npm's update notice. Before, a failed first run could reportnpm noticeas the error.#1101
84873d5Thanks @HugoRCD! - The CLI says what is wrong with the environment it is started in, and its output behaves in a pipe.@evlog/cli needs Node.js 22.0.0 or later, and this is Node.js 20.20.2and exit code 1. Before,evlog mapfailed there with a syntax error aboutglobSync, whiledoctor,logsand--versionstill ran on a Node the package does not support.evlog doctorno longer has a failingnodecheck or acli.NODE_TOO_OLDfinding, since it never starts there.package.jsonthat does not parse in the working directory no longer stops the launcher withERR_INVALID_PACKAGE_CONFIG.--helpprints to stdout, soevlog --help | grep mapworks. Usage shown with a usage error stays on stderr. Flags are listed the way they are typed (--min-score,-f, --follow), and positional arguments have their own section.evlog doctor 2> report.txtwrites plain text from a terminal.FORCE_COLOR=0andTERM=dumbturn colour off, and the header rule uses 24-bit colour only where the terminal supports it.evlog logs --json | head, ends the run quietly instead of with an unhandledEPIPEerror.#1059
4466f57Thanks @HugoRCD! - Every command now stops on a flag it does not declare, and on a value flag passed with no value, with exit code 2.evlog map --min-scor 90used to run with no gate and exit 0, andevlog init --dryrunwrote files. A flag written before the command name is checked too:evlog --dry-run initused to runinitfor real. A script that carries a mistyped flag today starts failing: fix the spelling.The other usage errors exit 2 as well, as the README documents: an unknown command, an invalid
--min-score,--framework,--formator--limit, andevlog map <entry>for an entry point that does not exist. An empty--min-score, which is what an unset shell variable expands to, is one of them. A bare--baselineno longer takes the flag after it as its value:evlog map --baseline --min-score 80andevlog map --baseline --cwd apps/webread both flags. Amaperror is printed as JSON under--format json, as it already was under--json.#1085
03b63a8Thanks @HugoRCD! -evlog logsreads a log of any size without its memory growing with it. Every view held each matching event until the end of the run: an 800 MB log took 1.2 GB with--limit 1. A view now keeps only the--limitevents it shows, andstatskeeps one duration per event for the percentiles. The output of every view is unchanged.#1083
9621ea4Thanks @HugoRCD! -evlog logsapplies every--wherewhen the flag is repeated. Only the last clause applied, so--where path=/a --where n=5returned events on any path. An empty--where, which is what an unset shell variable expands to, is now a usage error with exit 2.An event whose
duration,levelorserviceis not text no longer crashes every view,--jsonincluded.A
--wherevalue is a number only when it spells one exactly.zip=123no longer matches"00123", a 19-digit id no longer matches its neighbours, andamount>5000no longer matches a field that holds text such as"n/a". Write the value as the field holds it:zip=00123.#1113
6011cd1Thanks @HugoRCD! -evlog mapscores each entry point on its own handler instead of on the whole file.route.ts, server actions, TanStack Start methods), one instrumented handler used to pass every other one in the file, and each route listed the sameevent.fields. Each entry point is now read from its handler and the functions, classes and constants of the same file it names. An import such asstripemarks only the handlers that use it as sensitive.request.log.info()in a Fastify app that never registers evlog's plugin no longer passeswide-event: that is Fastify's own logger.req.logandrequest.logcount when the app registers evlog's middleware, or when the call isset,auditorfork.request.evlogis recognised.c.get('log').set()called without binding the logger first is credited in Hono.evlog map --allnames each row of a shared file by its route (index.ts · GET /health).evlog map <file>lists the other entry points of the file, andevlog map "POST /orders"inspects one by method and path.Scores drop in files where an instrumented route was covering for the others, so the rule-set version moves to 3.
--baselineagainst a map written by an earlier CLI exits 2 with the version mismatch: runevlog maponce and commit the newevlog.map.json.#1059
4466f57Thanks @HugoRCD! -evlog mapno longer scores a tree it only partly read.<file> failed to parseand counts the file as one failing entry point. With--min-score,map.minScoreor--baseline, the run stops withcli.MAP_PARSE_FAILED, exits 1, and leavesevlog.map.jsonas it was. List the file undermap.ignorewhen it is not app code.build,distandcoverageare skipped at the project root only, soserver/api/build/index.get.tsis scanned.get('/')in two routers, get distinct ids.--baselinereported regressions on an unchanged tree when they shared one. The id of every other entry point is unchanged, so a committed map stays comparable, and an entry point is still compared with itself when a second one with its method and path appears or goes. If it also moved to another file in that change, it is compared with the entry point that has its method and path and lost the most checks, then the lowest-scoring one..js,.mjsand.cjsfiles are parsed with JSX, so a Next.jspage.jsis checked instead of reported asn/a.The first and the last of these can change a verdict on code you did not touch, so the rule-set version moves to 2.
--baselineagainst a map written by an earlier CLI exits 2 with the version mismatch: runevlog maponce and commit the newevlog.map.json.#1059
4466f57Thanks @HugoRCD! - Newtelemetry.fail(code?)for a command that handles its own failure: it prints the error, sets an exit code and returns, so the run used to be recorded asoutcome: "success". Call it where the error is handled and the event carriesoutcome: "error"withcodeas itserrorCode.The evlog CLI calls it for every error it reports, so
evlog logswith no log directory,evlog configon an invalid file and a mistyped flag are sent as errors with theircli.*code. A failed--min-scoreor--baselinegate stays a successful run withmapGateFailed: true.#1059
4466f57Thanks @HugoRCD! - Telemetry now does what its docs say.telemetry disable, ordisableTelemetry()called inside a run, used to purge the outbox and then write its own event to it.disableTelemetry()turns off every handle created for the tool, and aflush()already sending stops at the batch in flight.EVLOG_TELEMETRY_DEBUG=1prints each run's event as the run ends and makes no request. The event is not queued either. It used to print at the next flush, and that flush sent the events.endpointhas to be the final URL.DO_NOT_TRACK=true,yesandonopt out like1, andEVLOG_TELEMETRY=false,noandofflike0.withTelemetry()records only the flags a command declares. An undeclared flag used to be sent by name, and a positional as<set>.binoption: the command people type, when it is notname. The first-run notice prints<bin> telemetry disable, so the evlog CLI's notice now saysevlog telemetry disable, notevlog-cli telemetry disable.evlog telemetry statuslists the allowlistedinit*,map*andlogs*values. The fieldsevlog logsrecords are documented.Updated dependencies [
777e3bb,4466f57,4466f57]:v0.11.2Compare Source
Patch Changes
#990
b4c170fThanks @HugoRCD! - Escape control characters inevlog logsoutput. Before, a logged value such as a request path containing\r\x1b[2Kwas printed to the terminal as is, so it could erase the line it was on and print a fake log line in its place. The one-line view, the full view of one event, itsFIELDSblock and thestatstable now print control characters as\r,\nand\u001b, the way evlog's pretty output does since its last patch. Tabs are kept.--jsonoutput is unchanged.#992
6f6e9dbThanks @HugoRCD! -evlog mapnow reads a Vue route file whose<script>block closes with</script >or another closing tag that has whitespace before>. Before, it found no script in that file and skipped it.v0.11.1Compare Source
Patch Changes
#945
17b0411Thanks @evlogai! -evlog initnow writesevlog.config.tswithprocess.env.NODE_ENVin place ofimport.meta.devfor Nuxt, Nitro and TanStack Start, the same condition Next, Hono, Express and Fastify already used. The generated file no longer reportsProperty 'dev' does not exist on type 'ImportMeta'in a fresh Nuxt project beforenuxi preparehas run. The production drain is still selected in a Nuxt production build, because Nitro inlinesNODE_ENVthere. Existingevlog.config.tsfiles are not rewritten; change the condition by hand to pick this up.#949
20aaa2cThanks @evlogai! -evlog logsand the NuxtHub log viewer now show the HTTP status of an error fromerror.status, falling back toerror.statusCodefor files written before v3. Before, a v3 error event rendered no status, and a 2.x error created with onlystatus(for example a plain h3 error) rendered none either.v0.11.0Compare Source
Minor Changes
#882
cf3a43bThanks @evlogai! -evlog initoffers Grafana Loki and ClickHouse as production destinations. Choosing one wirescreateLokiDrain()fromevlog/lokiorcreateClickHouseDrain()fromevlog/clickhouse, and asks forLOKI_ENDPOINTorCLICKHOUSE_ENDPOINT.#881
68d709aThanks @evlogai! -evlog initoffers Sazabi as a production destination. Choosing it wirescreateSazabiDrain()fromevlog/sazabiand asks forSAZABI_INTAKE_URL, the intake URL of an OpenTelemetry log stream in Sazabi.Patch Changes
#887
71b2d77Thanks @evlogai! -evlog doctorandevlog initnow recognise an app that reaches evlog only through a wrapper package, such as a shared@acme/loggerthat callscreateEvlog, the same wayevlog mapalready does.doctorreports evlog as reached through that package (for example "evlog via@acme/logger") instead of "not found in this project", drops thepnpm add evloghint, and no longer warns that the framework still needs evlog.initstops in that case and says evlog is already wired through the wrapper, rather than offering to install evlog and scaffold a second setup next to it.doctor --jsonreports the same result.#869
99189f3Thanks @HugoRCD! -evlog maprecognises evlog helpers imported from a package that wraps evlog, such as a shared@acme/loggerthat callscreateEvlogin a workspace. A dependency counts when it declaresevlogand forwards evlog's exports from one of itsexportsentries, whether as source or as built output. Handlers that importuseLoggerorwithEvlogfrom it are no longer reported as dark events, and an app that reaches evlog only through that package counts as having evlog installed. In a"use server"file, an export built by a call, such asexport const checkout = withEvlog(async () => …), is now listed as a server action.#895
6203a07Thanks @evlogai! - The published packages no longer ship.mapfiles. They pointed tosrc/, which is not part of the package, so they only added to the install size.evlogdrops from 340 files (about 2.09 MB unpacked) to 183 files (about 905 KB). No runtime or API change.Updated dependencies [
6203a07]:v0.10.0Compare Source
Minor Changes
#807
7e6282aThanks @HugoRCD! -evlog configreads the options passed to the evlog module innuxt.config.tsornitro.config.ts, which overrideevlog.config.tsat runtime. A note under the file name says so, and each setting they replace shows the value that applies with its line, and the value of the file under it.--jsonaddsmoduleOptionsand anoverrides: { value, source }field on those settings.#806
704c311Thanks @HugoRCD! -evlog mapandevlog logsreadevlog.config.ts(or.mts,.js,.mjs), the nearest one from the package up to the workspace root, without running it.map.rulesturns checks off or back on for every entry point,map.ignoreleaves entry points out by file glob and--jsonreports how many asignored,map.minScoreandmap.baselinegate like--min-scoreand--baseline, andlogs.dirandlogs.limitset the defaults of--dirand--limit. A flag wins over the config. The config can extend a local file or a published preset, one level deep.evlog configprints the settings that apply, grouped into service, sampling, redaction, pipeline and CLI, with the file and line each one comes from and evlog's defaults where the file says nothing,--jsonfor the same as JSON, andevlog doctorreports a config it cannot read. A misspelt setting, anextendswritten as a path instead of an imported config, a value undermaporlogscomputed at runtime, or turning offwide-eventorcontextstops the command with acli.CONFIG_*error. The CLI now needsevlog2.31.0 or later.#808
09b8d50Thanks @HugoRCD! -evlog initwritesevlog.config.tswith the service name, drains, enrichers and sampling you pick, dev and production branched in one place. Nuxt and Nitro load it through the module, and on Next.js, Hono, Express and Fastify the generatedevlog.tsimports it. In a workspace with a rootevlog.config.ts, the app config extends it and leaves out what the root already sets. A config you already have is read and never rewritten: a setting it lacks becomes a manual step, and the service it names becomes the default answer.#833
62637e9Thanks @evlogai! - A globalevlognow hands off to the@evlog/cliinstalled in the project it runs in, so a project always runs the CLI version it pins. In a directory with no install, the global copy runs as before.#831
b7b8c8bThanks @evlogai! -evlog agentsandevlog initnow install the agent skills globally by default, foruniversal(the shared.agents/skillsdirectory that Codex and the other agents read) andclaude-code(a symlink into it). Pass--localto install into the project instead, with.agents/skillsand.claude/skillsat the project root.Breaking:
--globalis removed, since global is now the default.evlog agentsno longer writesCLAUDE.md. Most agents readAGENTS.mddirectly, and Claude Code does too unless aCLAUDE.mdsits above it. Add a one-line@AGENTS.mdyourself if you want one; an existingCLAUDE.mdis left alone.Patch Changes
#824
75a32d8Thanks @evlogai! - Print the "evlog skills already installed" line once inevlog initandevlog agents. The plan already lists it, so the status line below now shows only thenpx skills updaterefresh command.#822
2d7503aThanks @evlogai! - Fix twoevlog mapresults.useLogger(event).set({ … })written inline, without binding the logger to a variable, is now credited as request context, so thecontextrule no longer reports the handler as missinglog.set(). A project with no entry points to score is now gradedunscored("nothing to scan") instead of a free "excellent" 100, and--min-scoreexits 1 in that case because there is nothing to meet the threshold against.#823
b603f28Thanks @evlogai! -evlog mapno longer draws a score for an unscored scan. A project with no entry points to score showed a full banner reading100and a full bar, next to "nothing to scan". The banner now draws--with an empty bar, and--allshows--in place of100/100. The JSON output and the--min-scoregate were already correct and are unchanged.#836
f3613eeThanks @HugoRCD! - Redact secrets by key name. A newsecretsbuilt-in, on by default with the other built-ins, replaces the value of any key ending inpassword,passwd,secretortoken(case-insensitive, at any depth) withreplacement. Sopassword,newPassword,client_secretandaccessTokenno longer reach production logs, while counters such astotalTokensandtokensPerSecondare kept. Values are replaced in full, booleans andnullare left alone, and listingbuiltinswithout'secrets'turns it off.evlog configlistssecretsamong the built-ins.v0.9.0Compare Source
Minor Changes
#773
a053adbThanks @HugoRCD! -evlog map --jsonnow carriesgradenext tomapandsummary, the same word the report prints, so a consumer no longer recomputes it from the score.--baseline-label <text>names the baseline in the report and the--format githubannotations when the map was copied to a temp file, so CI can sayregressed against maininstead of printing a path.#774
5ca8bd4Thanks @HugoRCD! -evlog logsreads the wide events the fs drain wrote to.evlog/logs: the last 50 (evlog logs), the failures (evlog logs errors), the slowest (evlog logs slow --over 1s), one request in full by id (evlog logs <requestId>, a UUID prefix is enough), or the shape of the traffic (evlog logs stats: per route, status class and level). Filters compose with every view:--since 15m,--until,--level error,fatal,--path,--status 5xx,--where payment.amount>5000on any field of the event (=,!=,>,>=,<,<=,~regex, present,!absent, repeatable),--limit,--dir.-ffollows new events liketail -f;--jsonreturns the events as JSON. It finds the project's log directory the waydoctordoes, reads every app of a workspace when the root has none, reads the memory drain's dev endpoint with--url(a follow there survives the app restarting, and says so when the endpoint stays quiet), handles both the compact and the pretty layout, and never writes.Patch Changes
302fd0e]:Configuration
📅 Schedule: (in timezone UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.