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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v2.11.4

Compare Source

Bug Fixes

• deps: update dependency framer-motion to ^11.16.4 (#​1558) (8c69ed3)

---

Configuration

📅 Schedule: Branch creation - "every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ Rebasing: Whenever PR becomes conflicted, 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 20, 2025 1:01pm
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 20, 2025 1:01pm
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 20, 2025 1:01pm

2 Skipped Deployments

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

[github-actions]

No changes to documentation

[socket-security]

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

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

View full report↗︎

[github-actions]

Component Testing Report Updated Jan 20, 2025 1:09 PM (UTC)

❌ Failed Tests (4) -- expand for details

File	Status	Duration	Passed	Skipped	Failed
comments/CommentInput.spec.tsx	✅ Passed (Inspect)	1m 11s	15	0	0
formBuilder/ArrayInput.spec.tsx	✅ Passed (Inspect)	12s	3	0	0
formBuilder/inputs/PortableText/Annotations.spec.tsx	❌ Failed (Inspect)	1m 59s	4	0	2
formBuilder/inputs/PortableText/copyPaste/CopyPaste.spec.tsx	❌ Failed (Inspect)	52s	9	7	2
formBuilder/inputs/PortableText/copyPaste/CopyPasteFields.spec.tsx	✅ Passed (Inspect)	0s	0	12	0
formBuilder/inputs/PortableText/Decorators.spec.tsx	✅ Passed (Inspect)	26s	6	0	0
formBuilder/inputs/PortableText/DisableFocusAndUnset.spec.tsx	✅ Passed (Inspect)	14s	3	0	0
formBuilder/inputs/PortableText/DragAndDrop.spec.tsx	✅ Passed (Inspect)	27s	6	0	0
formBuilder/inputs/PortableText/FocusTracking.spec.tsx	✅ Passed (Inspect)	1m 7s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	1m 31s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	2m 2s	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	✅ 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 Mon, 20 Jan 2025 13:13:39 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	24.7 efps (41ms)	25.6 efps (39ms)	-2ms (-3.7%)	✅
article (body)	72.5 efps (14ms)	67.6 efps (15ms)	+1ms (-/-%)	✅
article (string inside object)	27.0 efps (37ms)	27.0 efps (37ms)	+0ms (-/-%)	✅
article (string inside array)	25.0 efps (40ms)	23.0 efps (44ms)	+4ms (+8.8%)	✅
synthetic (title)	18.3 efps (55ms)	19.6 efps (51ms)	-4ms (-6.4%)	✅
synthetic (string inside object)	20.0 efps (50ms)	20.2 efps (50ms)	-1ms (-1.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)	41ms	51ms	70ms	583ms	998ms	11.7s
article (body)	14ms	16ms	23ms	139ms	181ms	5.3s
article (string inside object)	37ms	39ms	53ms	104ms	135ms	6.6s
article (string inside array)	40ms	43ms	46ms	143ms	133ms	6.6s
synthetic (title)	55ms	61ms	87ms	326ms	1026ms	13.1s
synthetic (string inside object)	50ms	53ms	56ms	425ms	991ms	8.2s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	39ms	49ms	69ms	398ms	746ms	11.9s
article (body)	15ms	17ms	23ms	148ms	194ms	5.1s
article (string inside object)	37ms	39ms	41ms	160ms	129ms	6.6s
article (string inside array)	44ms	45ms	55ms	99ms	307ms	7.1s
synthetic (title)	51ms	52ms	56ms	299ms	694ms	12.3s
synthetic (string inside object)	50ms	52ms	66ms	443ms	601ms	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.