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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v2.10.17

Compare Source

Bug Fixes

• typings: use React.JSX namespace (#​1543) (f42b6ab)

---

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

1 Skipped Deployment

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

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/ui@2.10.17	Transitive: environment	+19	14.6 MB	armandocerna, ash, atombender, ...62 more

🚮 Removed packages: npm/@sanity/ui@2.10.16

View full report↗︎

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Jan 3, 2025 4:12 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 28s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	1m 40s	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 16:14:10 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	27.0 efps (37ms)	28.6 efps (35ms)	-2ms (-5.4%)	✅
article (body)	52.9 efps (19ms)	55.9 efps (18ms)	-1ms (-5.3%)	✅
article (string inside object)	28.6 efps (35ms)	28.2 efps (36ms)	+1ms (+1.4%)	✅
article (string inside array)	25.0 efps (40ms)	25.0 efps (40ms)	+0ms (-/-%)	✅
recipe (name)	52.6 efps (19ms)	58.8 efps (17ms)	-2ms (-10.5%)	✅
recipe (description)	58.8 efps (17ms)	62.5 efps (16ms)	-1ms (-5.9%)	✅
recipe (instructions)	99.9+ efps (6ms)	99.9+ efps (7ms)	+1ms (-/-%)	✅
synthetic (title)	18.9 efps (53ms)	19.6 efps (51ms)	-2ms (-3.8%)	✅
synthetic (string inside object)	18.5 efps (54ms)	20.0 efps (50ms)	-4ms (-7.4%)	✅

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)	37ms	40ms	52ms	557ms	188ms	10.6s
article (body)	19ms	21ms	28ms	176ms	225ms	5.6s
article (string inside object)	35ms	38ms	42ms	155ms	130ms	6.5s
article (string inside array)	40ms	42ms	45ms	162ms	139ms	6.7s
recipe (name)	19ms	20ms	22ms	49ms	30ms	7.0s
recipe (description)	17ms	19ms	21ms	27ms	0ms	4.4s
recipe (instructions)	6ms	8ms	10ms	31ms	0ms	3.2s
synthetic (title)	53ms	55ms	62ms	132ms	575ms	13.3s
synthetic (string inside object)	54ms	57ms	73ms	611ms	956ms	8.9s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	35ms	38ms	49ms	370ms	779ms	9.5s
article (body)	18ms	22ms	34ms	170ms	223ms	5.3s
article (string inside object)	36ms	37ms	43ms	196ms	230ms	6.4s
article (string inside array)	40ms	42ms	48ms	151ms	144ms	7.0s
recipe (name)	17ms	19ms	21ms	36ms	0ms	6.3s
recipe (description)	16ms	17ms	19ms	33ms	0ms	4.3s
recipe (instructions)	7ms	9ms	10ms	54ms	0ms	3.4s
synthetic (title)	51ms	54ms	59ms	322ms	201ms	12.4s
synthetic (string inside object)	50ms	52ms	66ms	321ms	449ms	8.0s

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