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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v2.12.3

Compare Source

Bug Fixes

• deps: update React Compiler dependencies 🤖 ✨ (#​1595) (e2ea093)

---

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	Feb 10, 2025 11:50am
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 10, 2025 11:50am
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 10, 2025 11:50am

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 11:50am
test-next-studio	⬜️ Ignored (Inspect)			Feb 10, 2025 11:50am

[github-actions]

No changes to documentation

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	42.44%	53803 / 126771
🔵	Statements	42.44%	53803 / 126771
🔵	Functions	47.94%	2772 / 5782
🔵	Branches	78.83%	10320 / 13091

File Coverage

No changed files found.

Generated in workflow #30067 for commit 99d4028 by the Vitest Coverage Report Action

[github-actions]

Component Testing Report Updated Feb 10, 2025 11:49 AM (UTC)

❌ Failed Tests (51) -- expand for details

File	Status	Duration	Passed	Skipped	Failed
comments/CommentInput.spec.tsx	❌ Failed (Inspect)	39s	10	0	5
formBuilder/ArrayInput.spec.tsx	❌ Failed (Inspect)	7s	2	0	1
formBuilder/inputs/PortableText/Annotations.spec.tsx	❌ Failed (Inspect)	2m 19s	1	0	5
formBuilder/inputs/PortableText/copyPaste/CopyPaste.spec.tsx	❌ Failed (Inspect)	50s	11	1	6
formBuilder/inputs/PortableText/copyPaste/CopyPasteFields.spec.tsx	✅ Passed (Inspect)	0s	0	12	0
formBuilder/inputs/PortableText/Decorators.spec.tsx	❌ Failed (Inspect)	15s	4	0	2
formBuilder/inputs/PortableText/DisableFocusAndUnset.spec.tsx	❌ Failed (Inspect)	8s	2	0	1
formBuilder/inputs/PortableText/DragAndDrop.spec.tsx	❌ Failed (Inspect)	16s	4	0	2
formBuilder/inputs/PortableText/FocusTracking.spec.tsx	❌ Failed (Inspect)	40s	10	0	5
formBuilder/inputs/PortableText/Input.spec.tsx	❌ Failed (Inspect)	55s	14	0	7
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	❌ Failed (Inspect)	1m 15s	14	0	7
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx	❌ Failed (Inspect)	8s	2	9	1
formBuilder/inputs/PortableText/Styles.spec.tsx	❌ Failed (Inspect)	16s	4	0	2
formBuilder/inputs/PortableText/Toolbar.spec.tsx	❌ Failed (Inspect)	1m 1s	14	0	7
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, 10 Feb 2025 11:51:26 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	28.6 efps (35ms)	28.6 efps (35ms)	+0ms (-/-%)	✅
article (body)	74.9 efps (13ms)	81.3 efps (12ms)	-1ms (-/-%)	✅
article (string inside object)	29.4 efps (34ms)	28.6 efps (35ms)	+1ms (+2.9%)	✅
article (string inside array)	26.3 efps (38ms)	25.6 efps (39ms)	+1ms (+2.6%)	✅
recipe (name)	52.6 efps (19ms)	54.1 efps (19ms)	-1ms (-2.6%)	✅
recipe (description)	58.8 efps (17ms)	62.5 efps (16ms)	-1ms (-5.9%)	✅
recipe (instructions)	99.9+ efps (5ms)	99.9+ efps (5ms)	+0ms (-/-%)	✅
synthetic (title)	19.6 efps (51ms)	18.9 efps (53ms)	+2ms (+3.9%)	✅
synthetic (string inside object)	19.6 efps (51ms)	19.6 efps (51ms)	+0ms (-/-%)	✅

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)	35ms	37ms	42ms	263ms	246ms	10.1s
article (body)	13ms	15ms	17ms	133ms	175ms	5.0s
article (string inside object)	34ms	39ms	47ms	258ms	323ms	6.6s
article (string inside array)	38ms	40ms	47ms	89ms	232ms	6.6s
recipe (name)	19ms	21ms	38ms	62ms	2ms	7.8s
recipe (description)	17ms	18ms	20ms	31ms	0ms	4.4s
recipe (instructions)	5ms	6ms	8ms	31ms	0ms	3.0s
synthetic (title)	51ms	58ms	102ms	448ms	1325ms	13.4s
synthetic (string inside object)	51ms	54ms	58ms	293ms	753ms	8.3s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	35ms	37ms	42ms	448ms	259ms	10.4s
article (body)	12ms	14ms	19ms	140ms	173ms	4.8s
article (string inside object)	35ms	38ms	44ms	276ms	320ms	6.7s
article (string inside array)	39ms	40ms	45ms	49ms	16ms	6.3s
recipe (name)	19ms	21ms	24ms	38ms	2ms	7.8s
recipe (description)	16ms	17ms	18ms	27ms	0ms	4.3s
recipe (instructions)	5ms	7ms	9ms	24ms	0ms	3.0s
synthetic (title)	53ms	58ms	68ms	227ms	1012ms	13.2s
synthetic (string inside object)	51ms	56ms	60ms	467ms	1220ms	8.7s

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