Repository navigation
chore: merge main into v3 - #1185
Conversation
…and reply in the asker's language (#1167) Co-authored-by: linear-code[bot] <222613912+linear-code[bot]@users.noreply.github.com>
Co-authored-by: evlogai[bot] <313167257+evlogai[bot]@users.noreply.github.com>
…and code channels (#1183)
Co-authored-by: Hugo Richard <hrichard206@gmail.com>
…v3-2.37 Amp-Thread-ID: https://ampcode.com/threads/T-01a1fb0e-3558-77b8-88e4-7c86b981cf59 # Conflicts: # apps/docs/content/3.cli/10.logs.md # apps/evi/agent/tools/set-vercel-env.ts # packages/cli/package.json # packages/cli/src/commands/logs.ts # packages/cli/src/lib/errors.ts # packages/cli/src/lib/logs/render.ts # packages/evlog/src/adapters/otlp.ts # packages/evlog/src/nitro-v3/plugin.ts # packages/evlog/test/frameworks/fastify.test.ts # packages/signals/package.json # skills/analyze-logs/SKILL.md
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
|
Thank you for following the naming conventions! 🙏 |
Risk score: Very high (4/4)Assessed at 987f43a from the changed files and the title, by
|
@evlog/cli
@evlog/eve
evlog
@evlog/nuxthub
@evlog/signals
@evlog/telemetry
commit: |
Brings the 14 commits on
mainthatv3doesn't have intov3: the@evlog/signals0.3 work (#1170, #1171, #1173, #1174, #1177),evlog logs --ask(#1172), OTLPpartialSuccess(#1162), the shutdown flush for drain pipelines (#1165),log.discard()andemit: 'onError'(#1176), three Evi changes (#1167, #1180, #1183) and two repo-guidance commits (#1164, #1175). Like #1163, this lands by fast-forwardingv3to this branch's head, not by a squash, somainstays an ancestor ofv3.To check that after the fast-forward:
To try the one combination neither branch had,
--askon Vercel logs, install this PR's CLI with the two packages--askloads from beside it, then run it in a Vercel-linked project:How the conflicts were resolved
Peer ranges:
@evlog/signalstakes main'sai >=7.0.130and keepsevlog ^3.0.0-beta.0.@evlog/clikeeps v3'sevlogpeer (main never changed it) and adds main's optional peers, with the signals range widened so it accepts v3's own1.0.0-beta.0, which>=0.2.0alone rejects:evlog logs(feat(cli): rank logs by a question with evlog logs --ask #1172 against v3's Vercel source, sessions view and--expect): both sets of features are kept. The--askstep now runs on the Vercel read as well as on files and URLs, and--askis refused on thesessionsview as it already was onstats. Exit codes go through v3'sisUsageError, withLOGS_ASK_UNSUPPORTEDadded to the usage set, which gives main's exit codes.--jsoncarriescoverageandnotes, thensessions,stats,estimate,answersorevents. The CLI docs page and theanalyze-logsskill describe both.nitro-v3 plugin: keeps v3's request-logger resolver and main's
closehook that flushes pending drains.OTLP: main's
partialSuccessreaders go on top of v3's compact OTLP defaults.Small ones: the fastify test imports are merged, and Evi's
set-vercel-envkeeps v3's comment, which also mentions the logs tool.apps/docs/content/7.reference/9.migrate-v3.mdis unchanged, and.changeset/v3-removal-warnings.mdstays deleted. #1145's three changesets stay, because 2.37.0 (#1157) isn't on npm yet; the first sync after it ships should delete them, and the same goes for this sync'sotlp-partial-success,drain-shutdown-flushandquiet-units-discardif beta releases consume them first. The lockfile is regenerated fromv3's copy and only adds the CLI's two new dev dependencies.packages/cli/test/logs.vercel.test.tsgets one test for the new combination,--ask --dry-runon--source verceland the refusal on thesessionsview. With theaskcall removed from the Vercel path it failed (1 failed, 42 passed); with it, 43 passed.Bundle-size budget
No raise this time. Output of
pnpm --filter evlog run size:budgetat this branch's head:create-loggerandhonoare within 60 bytes of their budgets now, so the next sync may need a raise.Not run: e2e (it runs on the push to
v3) and the Evi evals. Evi's changes here come frommain, where they already merged.ELI5
Several changes landed on the 2.x branch, so this copies them into the 3.0 branch. Where both branches changed the same
evlog logscommand, it keeps both sets of features, and one new combination (asking a question about Vercel logs) gets a test.