Repository navigation
chore: merge main into v3 - #1121
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
|
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 8e83180 from the changed files and the title, by
|
|
Thank you for following the naming conventions! 🙏 |
@evlog/cli
evlog
@evlog/nuxthub
@evlog/signals
@evlog/telemetry
commit: |
Amp-Thread-ID: https://ampcode.com/threads/T-01a1e64f-4c92-704d-8d7c-f2c382342042 # Conflicts: # .github/workflows/ci.yml # .github/workflows/e2e.yml # apps/docs/content/3.cli/2.map.md # packages/evlog/test/e2e/README.md
…-beta3b Amp-Thread-ID: https://ampcode.com/threads/T-01a1e64f-4c92-704d-8d7c-f2c382342042 # Conflicts: # packages/evlog/bench/baseline/size-budget.json
…-beta3b Amp-Thread-ID: https://ampcode.com/threads/T-01a1e64f-4c92-704d-8d7c-f2c382342042 # Conflicts: # packages/cli/bin/evlog.mjs # packages/cli/test/bin.test.ts # packages/evlog/bench/baseline/size-budget.json
Brings the rest of
main(up to #1106) intov3before beta.3 (#1017). #1120 already syncedmainup to #1101 intov3(cb0d1f27), so this branch now adds only #1104 (use-cases diagram), #1110 (errorHandler: false), #1108 (fs rotation after cleanup), #1113 (evlog mapscores each entry point on its own handler) and #1106 (drain e2e suites), plus the two changeset fixes below. Like #1086 and #1088, it lands by fast-forwardingv3to this branch's head, not by a squash;cb0d1f27is merged in, so it still fast-forwards.Conflicts
src/nitro-v3/plugin.tsonDispose, still passing the recorded error toemitWithTailSamplingfor #1067's request-finish hooksrc/nuxt/module.tsclientEnabledand #1110'serrorHandler !== falseonv3's paths (../nitro/*on Nitro 3,../nitro/v2/*otherwise);main'saxiom.tokenwarning dropped, asv3removed itpackages/evlog/package.jsonv3's NestJS 12 dev dependencies and peers kept;main's other dev bumps taken. Peer ranges are unchanged fromv3docs/3.cli/0.overview.md--no-headerspelling with #1105's "Experimental" label.github/workflows/ci.yml,e2e.yml,test/e2e/README.md,docs/3.cli/2.map.mdv3'sBETTER_STACK_API_KEYname plus #1106'sHYPERDX_API_KEY; #1113's"METHOD /path"entry form withv3's exit-2 sentencerenovate.jsonv3's rule descriptionpnpm-lock.yamlmain'sFixes the merge needed
CLI launcher. #1120 fixed the launcher's evlog floor on
v3with its ownfloorOfhelper, so this branch takesv3'spackages/cli/bin/evlog.mjsandtest/bin.test.tsunchanged.Tests from
main, adjusted tov3. Theclient: falseanderrorHandler: falsetests run on Nitro 2, so they now expect../nitro/v2/*.v3's Effectmapsnapshot (#1102) gains #1075'seventkey.configureHandlerstays exported onv3, becausev3'ssilent-drain-warning.test.ts(#973) imports it; #1093 un-exported it onmain.Size budget. No budget changes left: #1120's budgets already cover this branch. Measured with
pnpm --filter evlog run size:budgetat the head:v3)Other. #1113 moves
evlog map's rule set to version 3, sov3's Effect snapshot now recordsruleSetVersion: 3.Changesets. These two still differ from
v3after #1120, and #1017's current changelog repeats both.restore-peer-floors.mdis deleted:v3's peers already accept those versions, and itshono >=4.13.17contradictsv3's range.nitro-v3-stream-emit.mdandnitro-error-handler-opt-out.mdnow namev3's subpaths. The new Nitro docs snippet usesdefineConfigfromnitro, as the rest ofv3's page does.Validation
pnpm run lint,pnpm run typecheck,pnpm run build:package: exit 0cb0d1f27, lint and typecheck pass;test/e2e/fs.e2e.ts6/6, telemetry 108/108, signals 33/33pnpm api:snapshot: unchangedmasks tokens in linear timeinredact-integration.test.tsfailed once under full-suite load (ratio 25.9 against a cap of 24), as it did onv3's CI at54c67ad. It passes 10/10 on its own.ELI5
More fixes landed on the 2.x branch, so this copies them into the 3.0 branch before the next beta. One of them, a startup check in the command-line tool, read the 3.0 version rules wrong and let any version through; that is fixed here.