Repository navigation
chore: merge main into v3 - #1163
Conversation
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: evlogai[bot] <313167257+evlogai[bot]@users.noreply.github.com>
…ntry rate limits (#1145)
|
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
|
Risk score: High (3/4)Assessed at 09000ac from the changed files and the title, by
|
|
Thank you for following the naming conventions! 🙏 |
@evlog/cli
@evlog/eve
evlog
@evlog/nuxthub
@evlog/signals
@evlog/telemetry
commit: |
Brings the 12 commits on
mainthatv3doesn't have intov3: 2.36.0's version PR (#1016), the v3 removal warnings for 2.x (#1150), drain retry rules, drop reporting and Sentry rate limits (#1145), the Evi bumps (#1138, #1143), the supported-versions table inSECURITY.md(#1159), an AGENTS.md rule (#1155), an Evi ledger (#1161), and four CI commits already onv3(#1140, #1144, #1146, #1152). Like #1135, this lands by fast-forwardingv3to this branch's head, not by a squash, somainstays an ancestor ofv3.To check that after the fast-forward:
How the conflicts were resolved
v3keeps its own version of every file feat: warn about every v3 removal and publish what's coming in v3 #1150 touches, and.changeset/v3-removal-warnings.mdis dropped.v3already removed those APIs, the "Changes in 3.0" callouts don't belong in the 3.0 docs, andapps/docs/content/7.reference/9.migrate-v3.mdstays the real 3.0 guide (so docs: tell readers to upgrade to the latest evlog 2 before v3 #1151 won't conflict).v3's package versions stay. The 2.36.0,@evlog/cli0.12.0 and@evlog/telemetry0.4.0 changelog sections go below the betas, as earlier syncs did. The 32 changesets 2.36.0 consumed are deleted here: all 32 are in.changeset/pre.jsonand already shipped in 3.0.0-beta.3, including the four Nitro onesv3had reworded.@github-tools/eve-extension0.15.0 and@vercel/connect2.9.4, and keeps its@evlog/eveworkspace dependency, whoseevepeer is>=1.0.0. The lockfile is regenerated fromv3's copy.custom-drains.mdkeepsv3's "drain" wording and adds main'sRetry-AfterandDrainDeliveryErrorrow. The API surface snapshot keeps bothonErrorCreated(v3) andparseRetryAfter(main).#1145's three patch changesets (
drain-retry-rules,pipeline-drop-reasons,sentry-rate-limits) stay, so the next beta ships them. Once 2.37.0 (#1157) is on npm, the next sync should delete them.Bundle-size budget
#1145 grows the shared HTTP and pipeline code, which puts the
axiomscenario over the budget that onlyv3enforces (test/build/size-budget.test.ts). This raises its budget from 13,500 to 13,750 gzip bytes, as #1120/#1121 did. It is still 5.2% under evlog@2.35.1. Output ofpnpm --filter evlog run size:budgetat this branch's head, before the raise:No published package source changes other than #1145's, so the only changesets are #1145's own.
packages/evlog/src/redact.tsis identical tov3's, so the redact bench doesn't move. On an orb, the "event holding a Date" row ran at 71–74k ops/s onv3and 75–79k withmain'sredact.ts. CI doesn't run that bench. The Evi evals were not run: the only Evi changes are dependency bumps and a ledger.ELI5
Several changes landed on the 2.x branch, so this copies them into the 3.0 branch. Where 2.x only warns about things that 3.0 already removed, the 3.0 version wins. One bundle got slightly bigger from the new retry logic, so its size limit goes up a little.