Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency @sanity/visual-editing-csm to ^2.0.9 #8954

Merged
merged 1 commit into from
Mar 17, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 17, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sanity/visual-editing-csm (source) ^2.0.8 -> ^2.0.9 age adoption passing confidence

Release Notes

sanity-io/visual-editing (@​sanity/visual-editing-csm)

v2.0.9

Dependencies

Configuration

📅 Schedule: Branch creation - "every weekday" (UTC), 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

Sorry, something went wrong.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@renovate renovate bot requested a review from a team as a code owner March 17, 2025 10:38
@renovate renovate bot requested review from jordanl17 and removed request for a team March 17, 2025 10:38
Copy link

vercel bot commented Mar 17, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
page-building-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 17, 2025 10:46am
performance-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 17, 2025 10:46am
test-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 17, 2025 10:46am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
studio-workshop ⬜️ Ignored (Inspect) Visit Preview Mar 17, 2025 10:46am
test-next-studio ⬜️ Ignored (Inspect) Mar 17, 2025 10:46am

@renovate renovate bot enabled auto-merge (squash) March 17, 2025 10:38
Copy link

@stipsan stipsan disabled auto-merge March 17, 2025 10:40
@stipsan stipsan merged commit 6c32d1a into next Mar 17, 2025
34 of 37 checks passed
@stipsan stipsan deleted the renovate/sanity-visual-editing-csm-2.x branch March 17, 2025 10:40
Copy link
Contributor

No changes to documentation

Copy link
Contributor

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 42.17% 54629 / 129528
🔵 Statements 42.17% 54629 / 129528
🔵 Functions 47.1% 2741 / 5819
🔵 Branches 79.39% 10220 / 12873
File CoverageNo changed files found.
Generated in workflow #32401 for commit b4a32fc by the Vitest Coverage Report Action

Copy link
Contributor

⚡️ Editor Performance Report

Updated Mon, 17 Mar 2025 10:53:40 GMT

Benchmark reference
latency of sanity@latest
experiment
latency of this branch
Δ (%)
latency difference
article (title) 25.6 efps (39ms) 23.8 efps (42ms) +3ms (+7.7%)
article (body) 68.3 efps (15ms) 77.5 efps (13ms) -2ms (-/-%)
article (string inside object) 24.4 efps (41ms) 24.1 efps (42ms) +1ms (+1.2%)
article (string inside array) 23.3 efps (43ms) 22.7 efps (44ms) +1ms (+2.3%)
recipe (name) 45.5 efps (22ms) 47.6 efps (21ms) -1ms (-4.5%)
recipe (description) 50.0 efps (20ms) 51.3 efps (20ms) -1ms (-2.5%)
recipe (instructions) 99.9+ efps (5ms) 99.9+ efps (5ms) +0ms (-/-%)
synthetic (title) 18.5 efps (54ms) 20.2 efps (50ms) -5ms (-8.3%)
synthetic (string inside object) 19.6 efps (51ms) 20.0 efps (50ms) -1ms (-2.0%)

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
article (title) 39ms 41ms 44ms 141ms 41ms 11.2s
article (body) 15ms 17ms 18ms 39ms 49ms 4.8s
article (string inside object) 41ms 43ms 48ms 142ms 186ms 6.8s
article (string inside array) 43ms 46ms 53ms 166ms 329ms 7.2s
recipe (name) 22ms 23ms 25ms 38ms 0ms 7.5s
recipe (description) 20ms 21ms 22ms 23ms 0ms 4.8s
recipe (instructions) 5ms 7ms 8ms 9ms 0ms 3.1s
synthetic (title) 54ms 57ms 63ms 214ms 925ms 13.8s
synthetic (string inside object) 51ms 53ms 58ms 129ms 516ms 7.8s

🧪 Experiment result

The performance result of this branch

Benchmark latency p75 p90 p99 blocking time test duration
article (title) 42ms 47ms 75ms 266ms 467ms 11.5s
article (body) 13ms 15ms 16ms 31ms 52ms 4.9s
article (string inside object) 42ms 43ms 46ms 50ms 55ms 7.0s
article (string inside array) 44ms 46ms 47ms 133ms 199ms 7.0s
recipe (name) 21ms 22ms 25ms 31ms 0ms 7.4s
recipe (description) 20ms 21ms 24ms 42ms 12ms 5.2s
recipe (instructions) 5ms 7ms 7ms 8ms 0ms 3.1s
synthetic (title) 50ms 53ms 56ms 93ms 497ms 14.9s
synthetic (string inside object) 50ms 51ms 58ms 491ms 1214ms 8.5s

📚 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.

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.

None yet

1 participant