fix(deps): update dependency @sanity/ui to ^2.10.15

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sanity/ui (source)	^2.10.14 -> ^2.10.15

---

Release Notes

sanity-io/ui (@​sanity/ui)

v2.10.15

Compare Source

Bug Fixes

• omit popover html attribute (4f1895e)

---

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 these updates 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 . View repository job log here

[vercel]

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	Jan 3, 2025 2:57pm
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 3, 2025 2:57pm
test-next-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 3, 2025 2:57pm
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 3, 2025 2:57pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Jan 3, 2025 2:57pm

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/[email protected]	Transitive: environment	+19	14.6 MB	sanity-io

🚮 Removed packages: npm/@sanity/[email protected]

View full report↗︎

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Jan 3, 2025 2:53 PM (UTC)

✅ All Tests Passed -- expand for details

File	Status	Duration	Passed	Skipped	Failed
comments/CommentInput.spec.tsx	✅ Passed (Inspect)	1m 3s	15	0	0
formBuilder/ArrayInput.spec.tsx	✅ Passed (Inspect)	12s	3	0	0
formBuilder/inputs/PortableText/Annotations.spec.tsx	✅ Passed (Inspect)	38s	6	0	0
formBuilder/inputs/PortableText/copyPaste/CopyPaste.spec.tsx	✅ Passed (Inspect)	50s	11	7	0
formBuilder/inputs/PortableText/copyPaste/CopyPasteFields.spec.tsx	✅ Passed (Inspect)	0s	0	12	0
formBuilder/inputs/PortableText/Decorators.spec.tsx	✅ Passed (Inspect)	25s	6	0	0
formBuilder/inputs/PortableText/DisableFocusAndUnset.spec.tsx	✅ Passed (Inspect)	14s	3	0	0
formBuilder/inputs/PortableText/DragAndDrop.spec.tsx	✅ Passed (Inspect)	26s	6	0	0
formBuilder/inputs/PortableText/FocusTracking.spec.tsx	✅ Passed (Inspect)	1m 6s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	1m 27s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	1m 41s	18	0	0
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx	✅ Passed (Inspect)	13s	3	9	0
formBuilder/inputs/PortableText/Styles.spec.tsx	✅ Passed (Inspect)	26s	6	0	0
formBuilder/inputs/PortableText/Toolbar.spec.tsx	✅ Passed (Inspect)	1m 43s	21	0	0
formBuilder/tree-editing/TreeEditing.spec.tsx	✅ Passed (Inspect)	0s	0	3	0
formBuilder/tree-editing/TreeEditingNestedObjects.spec.tsx	✅ Passed (Inspect)	0s	0	3	0

[github-actions]

⚡️ Editor Performance Report

Updated Fri, 03 Jan 2025 14:54:39 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	25.6 efps (39ms)	27.0 efps (37ms)	-2ms (-5.1%)	✅
article (body)	56.0 efps (18ms)	72.5 efps (14ms)	-4ms (-22.7%)	✅
article (string inside object)	25.6 efps (39ms)	29.4 efps (34ms)	-5ms (-12.8%)	✅
article (string inside array)	22.5 efps (45ms)	24.4 efps (41ms)	-4ms (-7.9%)	✅
recipe (name)	55.6 efps (18ms)	62.5 efps (16ms)	-2ms (-11.1%)	✅
recipe (description)	62.5 efps (16ms)	71.4 efps (14ms)	-2ms (-12.5%)	✅
recipe (instructions)	99.9+ efps (6ms)	99.9+ efps (5ms)	-1ms (-/-%)	✅
synthetic (title)	19.8 efps (51ms)	20.8 efps (48ms)	-3ms (-5.0%)	✅
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	42ms	53ms	445ms	855ms	10.3s
article (body)	18ms	21ms	23ms	70ms	216ms	5.4s
article (string inside object)	39ms	40ms	57ms	273ms	267ms	7.0s
article (string inside array)	45ms	47ms	52ms	165ms	267ms	7.3s
recipe (name)	18ms	20ms	22ms	42ms	0ms	6.8s
recipe (description)	16ms	17ms	19ms	30ms	0ms	4.3s
recipe (instructions)	6ms	7ms	8ms	10ms	0ms	3.1s
synthetic (title)	51ms	54ms	57ms	304ms	593ms	13.1s
synthetic (string inside object)	51ms	55ms	81ms	213ms	736ms	8.5s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	37ms	39ms	60ms	453ms	710ms	10.0s
article (body)	14ms	16ms	18ms	116ms	193ms	5.0s
article (string inside object)	34ms	35ms	40ms	50ms	139ms	6.3s
article (string inside array)	41ms	43ms	45ms	172ms	161ms	6.8s
recipe (name)	16ms	19ms	21ms	36ms	0ms	6.3s
recipe (description)	14ms	16ms	18ms	26ms	0ms	4.2s
recipe (instructions)	5ms	6ms	8ms	19ms	0ms	3.0s
synthetic (title)	48ms	51ms	61ms	355ms	619ms	12.1s
synthetic (string inside object)	50ms	52ms	61ms	175ms	284ms	7.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.