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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v2.11.6

Compare Source

Bug Fixes

• deps: update React Compiler dependencies 🤖 ✨ (#​1563) (8fe1bb6)

---

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 27, 2025 1:00pm
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 27, 2025 1:00pm
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 27, 2025 1:00pm

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Jan 27, 2025 1:00pm
test-next-studio	⬜️ Ignored (Inspect)			Jan 27, 2025 1:00pm

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/ui@2.11.6 🔁 npm/@sanity/ui@2.11.5	Transitive: environment	+22	10.3 MB	adoprog, armandocerna, ash, ...66 more

View full report↗︎

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Jan 27, 2025 1:03 PM (UTC)

❌ Failed Tests (2) -- 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	❌ Failed (Inspect)	1m 20s	5	0	1
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)	29s	6	0	0
formBuilder/inputs/PortableText/FocusTracking.spec.tsx	✅ Passed (Inspect)	1m 5s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	1m 32s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	2m 3s	21	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	❌ Failed (Inspect)	2m 23s	20	0	1
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 Mon, 27 Jan 2025 13:05:26 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	22.0 efps (46ms)	23.8 efps (42ms)	-4ms (-7.7%)	✅
article (body)	67.6 efps (15ms)	78.1 efps (13ms)	-2ms (-/-%)	✅
article (string inside object)	26.3 efps (38ms)	27.0 efps (37ms)	-1ms (-2.6%)	✅
article (string inside array)	22.7 efps (44ms)	22.7 efps (44ms)	+0ms (-/-%)	✅
recipe (name)	50.0 efps (20ms)	52.6 efps (19ms)	-1ms (-5.0%)	✅
recipe (description)	55.6 efps (18ms)	58.8 efps (17ms)	-1ms (-5.6%)	✅
recipe (instructions)	99.9+ efps (5ms)	99.9+ efps (5ms)	+0ms (-/-%)	✅
synthetic (title)	19.2 efps (52ms)	19.2 efps (52ms)	+0ms (-/-%)	✅
synthetic (string inside object)	19.4 efps (52ms)	20.0 efps (50ms)	-2ms (-2.9%)	✅

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)	46ms	56ms	65ms	488ms	804ms	11.2s
article (body)	15ms	17ms	18ms	96ms	84ms	5.0s
article (string inside object)	38ms	39ms	50ms	112ms	130ms	6.7s
article (string inside array)	44ms	46ms	54ms	194ms	312ms	7.2s
recipe (name)	20ms	22ms	29ms	48ms	0ms	7.4s
recipe (description)	18ms	19ms	20ms	28ms	0ms	4.4s
recipe (instructions)	5ms	6ms	7ms	7ms	0ms	3.0s
synthetic (title)	52ms	54ms	61ms	85ms	582ms	11.9s
synthetic (string inside object)	52ms	54ms	66ms	496ms	1058ms	8.3s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	42ms	53ms	71ms	454ms	753ms	10.7s
article (body)	13ms	14ms	18ms	52ms	65ms	4.6s
article (string inside object)	37ms	40ms	60ms	216ms	306ms	7.1s
article (string inside array)	44ms	47ms	55ms	254ms	371ms	7.3s
recipe (name)	19ms	20ms	22ms	38ms	0ms	7.0s
recipe (description)	17ms	18ms	21ms	38ms	0ms	4.3s
recipe (instructions)	5ms	6ms	8ms	21ms	0ms	3.0s
synthetic (title)	52ms	53ms	56ms	119ms	239ms	11.8s
synthetic (string inside object)	50ms	51ms	56ms	484ms	1024ms	8.1s

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