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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v2.11.1

Compare Source

Bug Fixes

• deps: update dependency framer-motion to ^11.16.0 (#​1553) (a388818)
• refactor ReactElement to JSX.Element types (#​1555) (a2317c5)

---

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 8, 2025 9:21am
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 8, 2025 9:21am
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 8, 2025 9:21am

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Jan 8, 2025 9:21am
test-next-studio	⬜️ Ignored (Inspect)			Jan 8, 2025 9:21am

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/ui@2.11.1	Transitive: environment	+22	10.3 MB	sanity-io

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

View full report↗︎

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Jan 8, 2025 9:21 AM (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 38s	18	0	0
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx	✅ Passed (Inspect)	12s	3	9	0
formBuilder/inputs/PortableText/Styles.spec.tsx	✅ Passed (Inspect)	25s	6	0	0
formBuilder/inputs/PortableText/Toolbar.spec.tsx	✅ Passed (Inspect)	1m 42s	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 Wed, 08 Jan 2025 09:22:01 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	21.1 efps (48ms)	25.6 efps (39ms)	-9ms (-17.9%)	✅
article (body)	46.8 efps (21ms)	46.9 efps (21ms)	-0ms (-0.2%)	✅
article (string inside object)	23.3 efps (43ms)	27.0 efps (37ms)	-6ms (-14.0%)	✅
article (string inside array)	20.4 efps (49ms)	23.3 efps (43ms)	-6ms (-12.2%)	✅
recipe (name)	44.4 efps (23ms)	50.0 efps (20ms)	-3ms (-11.1%)	✅
recipe (description)	47.6 efps (21ms)	55.6 efps (18ms)	-3ms (-14.3%)	✅
recipe (instructions)	99.9+ efps (6ms)	99.9+ efps (6ms)	+0ms (-/-%)	✅
synthetic (title)	17.9 efps (56ms)	18.9 efps (53ms)	-3ms (-5.4%)	✅
synthetic (string inside object)	17.9 efps (56ms)	19.8 efps (51ms)	-6ms (-9.8%)	✅

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)	48ms	55ms	79ms	606ms	1065ms	12.8s
article (body)	21ms	25ms	36ms	232ms	329ms	6.5s
article (string inside object)	43ms	46ms	52ms	105ms	340ms	7.6s
article (string inside array)	49ms	53ms	62ms	104ms	484ms	8.0s
recipe (name)	23ms	24ms	27ms	48ms	0ms	8.6s
recipe (description)	21ms	22ms	26ms	40ms	1ms	4.9s
recipe (instructions)	6ms	8ms	9ms	19ms	0ms	3.1s
synthetic (title)	56ms	59ms	64ms	112ms	821ms	13.5s
synthetic (string inside object)	56ms	61ms	77ms	417ms	1349ms	9.2s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	39ms	45ms	72ms	372ms	732ms	11.8s
article (body)	21ms	25ms	30ms	145ms	274ms	5.9s
article (string inside object)	37ms	38ms	43ms	164ms	134ms	6.8s
article (string inside array)	43ms	46ms	53ms	69ms	171ms	7.0s
recipe (name)	20ms	22ms	24ms	34ms	0ms	8.3s
recipe (description)	18ms	19ms	21ms	30ms	0ms	4.4s
recipe (instructions)	6ms	8ms	9ms	31ms	0ms	3.2s
synthetic (title)	53ms	55ms	60ms	124ms	506ms	12.7s
synthetic (string inside object)	51ms	53ms	74ms	512ms	1039ms	8.4s

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