Skip to content

chore: merge main into v3 - #1135

Merged
HugoRCD merged 4 commits into
v3from
chore/sync-main-into-v3-beta3d
Nov 18, 2026
Merged

HugoRCD merged 4 commits into
v3from
chore/sync-main-into-v3-beta3d

Conversation

@HugoRCD

@HugoRCD HugoRCD commented Nov 18, 2026

Copy link
Copy Markdown
Member

Written by an AI agent on behalf of @HugoRCD. @HugoRCD has not reviewed it yet.

Brings the three commits on main that v3 doesn't have into v3 before beta.3 (#1017): #1132 (content-lint keeps underscores in heading anchors), #1122 (re-measure a linear-time check before failing it on one noisy sample) and #1133 (drop an em dash from Evi's docs connection description). Like #1121 and #1129, this lands by fast-forwarding v3 to this branch's head, not by a squash, so main stays an ancestor of v3.

None of the three touches a published package or has a changeset, so beta.3's versions and changelog stay the same.

Conflict

packages/evlog/test/helpers/timers.ts and timers.test.ts: #1122 on main and #1118 on v3 both changed expectLinearTime. The code merged cleanly to both behaviours: v3's 32x ratio (#1118, for Node 22's slower long strings) and main's up to three measurements (#1122). Only the doc comment and two neighbouring tests conflicted:

  • The doc comment now says "at most 32x the shorter, on at least one of three measurements".
  • Both tests are kept. In main's "measures again" test the slow first sample is now 5x instead of 4x. At 4x the first ratio is exactly 32 (8 × 4), which misses v3's limit only because the check is strict <. At 5x (ratio 40) it misses clearly, so the test still proves the retry.
-      now += (input.length / 1_000) * (isLong && firstAttempt ? 4 : 1)
+      now += (input.length / 1_000) * (isLong && firstAttempt ? 5 : 1)

Validation

At this branch's head:

$ pnpm --filter evlog exec vitest run test/helpers/timers.test.ts
 ✓ |evlog| test/helpers/timers.test.ts (12 tests)
      Tests  12 passed (12)

With MAX_ATTEMPTS set to 1, the "measures again" test fails (1 failed | 11 passed), so it still checks the retry. CI runs the rest.

ELI5

Three small changes landed on the 2.x branch, so this copies them into the 3.0 branch before the next beta. Both branches had changed the same timing test helper in different ways, and this keeps both changes.

HugoRCD and others added 4 commits November 17, 2026 22:44
@vercel

vercel Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
evi Ready Ready Preview Nov 18, 2026 9:27am UTC
evlog-docs Ready Ready Preview, v0 Nov 18, 2026 9:27am UTC
evlog-render-lab Ready Ready Preview Nov 18, 2026 9:27am UTC
evlog-telemetry Ready Ready Preview Nov 18, 2026 9:27am UTC
just-use-evlog Ready Ready Preview Nov 18, 2026 9:27am UTC

Request Review

@coderabbitai

coderabbitai Bot commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 8e9e9720-791f-4e1f-ba58-22d247bf9175

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions

Copy link
Copy Markdown
Contributor

Risk score: Very high (4/4)

Assessed at 7f8e5d1 from the changed files and the title, by scripts/risk-score. A new push replaces this score.

  • On merge: deploys Evi
  • Evi agent: Access: changes who Evi trusts or which credentials it holds: connections/docs.ts
  • No test changed in Evi agent: connections/docs.ts
  • 6 files changed (50 lines), 4 of them tests
Area Level Why
Evi agent Very high Access: changes who Evi trusts or which credentials it holds: connections/docs.ts
CI and release Typical Tooling: changes repository scripts: lib/reach.mjs; Tests only: lib/reach.test.mjs
evlog core Low Tests only: test/README.md, helpers/timers.test.ts, helpers/timers.ts

@github-actions

Copy link
Copy Markdown
Contributor

Thank you for following the naming conventions! 🙏

@pkg-pr-new

pkg-pr-new Bot commented Nov 18, 2026

Copy link
Copy Markdown
@evlog/cli

npm i https://pkg.pr.new/evloghq/evlog/@evlog/cli@1135

@evlog/eve

npm i https://pkg.pr.new/evloghq/evlog/@evlog/eve@1135

evlog

npm i https://pkg.pr.new/evloghq/evlog@1135

@evlog/nuxthub

npm i https://pkg.pr.new/evloghq/evlog/@evlog/nuxthub@1135

@evlog/signals

npm i https://pkg.pr.new/evloghq/evlog/@evlog/signals@1135

@evlog/telemetry

npm i https://pkg.pr.new/evloghq/evlog/@evlog/telemetry@1135

commit: 7f8e5d1

@HugoRCD
HugoRCD merged commit 7f8e5d1 into v3 Nov 18, 2026
27 checks passed
@HugoRCD
HugoRCD deleted the chore/sync-main-into-v3-beta3d branch November 18, 2026 09:40
@HugoRCD
HugoRCD deployed to npm-publish November 18, 2026 09:40 — with GitHub Actions Active

This branch was successfully deployed

6 active deployments
npm-publish — 7f8e5d11 Deployed Nov 18, 2026 by HugoRCD via release #995
Preview – evi — 7f8e5d11 Deployed Nov 18, 2026 by vercel[bot]
Preview – evlog-docs — 7f8e5d11 Deployed Nov 18, 2026 by vercel[bot]
Preview – evlog-telemetry — 7f8e5d11 Deployed Nov 18, 2026 by vercel[bot]
Preview – just-use-evlog — 7f8e5d11 Deployed Nov 18, 2026 by vercel[bot]
Preview – evlog-render-lab — 7f8e5d11 Deployed Nov 18, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant