Skip to content

fix(deps): update dependency @sanity/comlink to ^4.0.3 - #13913

Open
squiggler-app[bot] wants to merge 1 commit into
mainfrom
renovate/sanity-comlink-4.x
Open

fix(deps): update dependency @sanity/comlink to ^4.0.3#13913
squiggler-app[bot] wants to merge 1 commit into
mainfrom
renovate/sanity-comlink-4.x

Conversation

@squiggler-app

@squiggler-app squiggler-app Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@sanity/comlink (source) ^4.0.1^4.0.3 age confidence

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here


Note

Low Risk
Patch-level dependency-only update with no code changes; comlink is used for studio/presentation messaging but semver patch bumps are typically backward compatible.

Overview
Bumps @sanity/comlink in the sanity package from ^4.0.1 to ^4.0.3, with the matching pnpm-lock.yaml entry updated to resolve 4.0.3. No application source changes—only dependency metadata.

Reviewed by Cursor Bugbot for commit 9eab428. Bugbot is set up for automated code reviews on this repo. Configure here.

@squiggler-app
squiggler-app Bot requested a review from a team as a code owner August 7, 2026 06:35
@squiggler-app
squiggler-app Bot requested review from stipsan and removed request for a team August 7, 2026 06:35
@squiggler-app
squiggler-app Bot enabled auto-merge (squash) August 7, 2026 06:35
@vercel

vercel Bot commented Aug 7, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
auth-test-studio Ready Ready Preview Aug 10, 2026 6:27pm
page-building-studio Ready Ready Preview Aug 10, 2026 6:27pm
studio-metrics Ready Ready Preview Aug 10, 2026 6:27pm
test-studio Ready Ready Preview Aug 10, 2026 6:27pm
test-studio-preview-iframe Ready Ready Preview Aug 10, 2026 6:27pm

Request Review

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

📦 Bundle Stats — sanity

Compared against main (e510c024) · v6.9.1 (npm)

sanity

Metric Value vs main (e510c02) vs v6.9.1
Internal (raw) 4.18 MB - +12.6 KB, +0.3%
Internal (gzip) 1.03 MB - +4.1 KB, +0.4%
Bundled (raw) 12.87 MB - -33.5 KB, -0.3%
Bundled (gzip) 3.02 MB - -38.4 KB, -1.2%
Import time 1.90s +1ms, +0.0% +134ms, +7.6%

bin:sanity

Metric Value vs main (e510c02) vs v6.9.1
Internal (raw) 7.1 KB - -
Internal (gzip) 2.9 KB - -
Bundled (raw) 7.1 KB - -
Bundled (gzip) 2.8 KB - -
Import time 5ms +0ms, +3.3% +0ms, +6.6%

🗺️ View treemap · Artifacts

Details
  • Import time regressions over 10% are flagged with ⚠️
  • Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

📚 TypeDoc Generation Result

TypeDoc generated successfully!

  • File size: 8.4M
  • Total exports: 1085
  • Artifact: sanity-typedoc-cff2d49b67985dadc28215d8742406e421b9740f

The TypeDoc JSON file has been generated and validated. All documentation scripts completed successfully.

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

❌ E2E Tests

🟢 136 passed🔴 15 failed🟡 54 flaky • (⚪ 101 skipped) • view full reportview run

Debug failing tests locally
SANITY_E2E_PROJECT_ID=ittbm412 \
SANITY_E2E_BASE_URL=https://e2e-studio-98qa7m8vb.sanity.dev \
SANITY_E2E_DATASET=pr-13913-chromium-31418991751 \
SANITY_E2E_DATASET_CHROMIUM=pr-13913-chromium-31418991751 \
SANITY_E2E_DATASET_FIREFOX=pr-13913-firefox-31418991751 \
pnpm test:e2e --headed \
  e2e/tests/desk/defaultPanes.spec.ts \
  e2e/tests/document-actions/delete.spec.ts \
  e2e/tests/document-actions/discardChanges.spec.ts \
  e2e/tests/document-actions/restore.spec.ts \
  e2e/tests/enhanced-object-dialog/deepLinkPath.spec.ts \
  e2e/tests/expanded-document/expanded.spec.ts \
  e2e/tests/navbar/search.spec.ts \
  e2e/tests/releases/displayDocument/DisplayedDocument.spec.ts \
  e2e/tests/validation-test/validation.spec.ts \
  e2e/tests/variants/variantTool.spec.ts

Studio: https://e2e-studio-98qa7m8vb.sanity.dev

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

⚡️ Editor Performance Report

Updated Mon, 10 Aug 2026 18:37:43 GMT

Benchmark reference
latency of sanity@latest
experiment
latency of this branch
Δ (%)
latency difference
arrayI18n (simple-en) 33.3 efps (30ms) 33.3 efps (30ms) +0ms (-/-%)
article (title) 31.3 efps (32ms) 30.3 efps (33ms) +1ms (+3.1%)
article (body) 27.1 efps (37ms) 27.2 efps (37ms) -0ms (-0.3%)
article (string inside object) 76.9 efps (13ms) 31.3 efps (32ms) +19ms (+146.2%) 🔴
article (string inside array) 64.5 efps (16ms) 51.3 efps (20ms) +4ms (+25.8%) 🔴
recipe (name) 90.9 efps (11ms) 34.5 efps (29ms) +18ms (+163.6%) 🔴
recipe (description) 50.0 efps (20ms) 43.5 efps (23ms) +3ms (+15.0%)
recipe (instructions) 83.7 efps (12ms) 99.9+ efps (8ms) -4ms (-/-%)
singleString (stringField) 99.9+ efps (10ms) 99.9+ efps (10ms) -1ms (-/-%)
synthetic (title) 33.3 efps (30ms) 33.3 efps (30ms) +0ms (-/-%)
synthetic (string inside object) 33.3 efps (30ms) 33.3 efps (30ms) +0ms (-/-%)

efps — editor "frames per second". The number of updates assumed to be possible within a second.

Derived from input latency. efps = 1000 / input_latency

Detailed information

🏠 Reference result

The performance result of sanity@latest

Benchmark latency p75 p90 p99 blocking time test duration
arrayI18n (simple-en) 30ms 32ms 35ms 42ms 10ms 9.0s
article (title) 32ms 37ms 43ms 259ms 443ms 16.0s
article (body) 37ms 41ms 48ms 72ms 205ms 8.5s
article (string inside object) 13ms 22ms 35ms 53ms 32ms 7.9s
article (string inside array) 16ms 28ms 35ms 76ms 43ms 8.3s
recipe (name) 11ms 14ms 16ms 28ms 61ms 5.8s
recipe (description) 20ms 24ms 29ms 38ms 0ms 4.6s
recipe (instructions) 12ms 17ms 24ms 38ms 0ms 3.6s
singleString (stringField) 10ms 14ms 17ms 23ms 17ms 4.5s
synthetic (title) 30ms 31ms 32ms 41ms 1818ms 13.3s
synthetic (string inside object) 30ms 31ms 38ms 80ms 1357ms 10.2s

🧪 Experiment result

The performance result of this branch

Benchmark latency p75 p90 p99 blocking time test duration
arrayI18n (simple-en) 30ms 32ms 37ms 43ms 0ms 9.2s
article (title) 33ms 37ms 41ms 243ms 401ms 15.0s
article (body) 37ms 39ms 44ms 62ms 268ms 8.4s
article (string inside object) 32ms 35ms 43ms 59ms 7ms 8.3s
article (string inside array) 20ms 29ms 37ms 55ms 88ms 8.2s
recipe (name) 29ms 31ms 33ms 38ms 65ms 8.2s
recipe (description) 23ms 29ms 32ms 45ms 0ms 5.1s
recipe (instructions) 8ms 12ms 14ms 31ms 0ms 3.2s
singleString (stringField) 10ms 13ms 15ms 25ms 2ms 4.3s
synthetic (title) 30ms 31ms 33ms 72ms 1380ms 12.7s
synthetic (string inside object) 30ms 31ms 32ms 36ms 933ms 9.6s

📚 Glossary

column definitions

  • benchmark — the name of the test, e.g. "article", followed by the label of the field being measured, e.g. "(title)".
  • latency — the time between when a key was pressed and when it was rendered. derived from a set of samples. the median (p50) is shown to show the most common latency.
  • p75 — the 75th percentile of the input latency in the test run. 75% of the sampled inputs in this benchmark were processed faster than this value. this provides insight into the upper range of typical performance.
  • p90 — the 90th percentile of the input latency in the test run. 90% of the sampled inputs were faster than this. this metric helps identify slower interactions that occurred less frequently during the benchmark.
  • p99 — the 99th percentile of the input latency in the test run. only 1% of sampled inputs were slower than this. this represents the worst-case scenarios encountered during the benchmark, useful for identifying potential performance outliers.
  • blocking time — the total time during which the main thread was blocked, preventing user input and UI updates. this metric helps identify performance bottlenecks that may cause the interface to feel unresponsive.
  • test duration — how long the test run took to complete.

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 44.38% 32361 / 72903
🔵 Statements 37.33% 42203 / 113033
🔵 Functions 35.69% 6871 / 19250
🔵 Branches 30.01% 28345 / 94425
File CoverageNo changed files found.
Generated in workflow #64582 for commit 9eab428 by the Vitest Coverage Report Action

@squiggler-app
squiggler-app Bot force-pushed the renovate/sanity-comlink-4.x branch from 16e5320 to ac2d73f Compare August 7, 2026 14:42
@squiggler-app
squiggler-app Bot force-pushed the renovate/sanity-comlink-4.x branch from ac2d73f to 3328dd9 Compare August 7, 2026 16:24
@squiggler-app
squiggler-app Bot force-pushed the renovate/sanity-comlink-4.x branch from 3328dd9 to 44cdfb2 Compare August 7, 2026 17:24
@squiggler-app
squiggler-app Bot force-pushed the renovate/sanity-comlink-4.x branch from 44cdfb2 to 580d634 Compare August 7, 2026 18:23
@squiggler-app
squiggler-app Bot force-pushed the renovate/sanity-comlink-4.x branch from 580d634 to 7b74b30 Compare August 10, 2026 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants