chore(deps): update dependency @sanity/visual-editing to v2.12.12

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sanity/visual-editing (source)	2.12.11 -> 2.12.12

---

Release Notes

sanity-io/visual-editing (@​sanity/visual-editing)

v2.12.12

Bug Fixes

• deps: update react compiler dependencies 🤖 ✨ (#​2604) (60f5349)

---

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (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 this update 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 4, 2025 0:27am
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 4, 2025 0:27am
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 4, 2025 0:27am

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Feb 4, 2025 0:27am
test-next-studio	⬜️ Ignored (Inspect)			Feb 4, 2025 0:27am

[github-actions]

No changes to documentation

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/[email protected]	environment, eval	+3	10 MB	sanity-io

View full report↗︎

[github-actions]

Component Testing Report Updated Feb 4, 2025 12:31 PM (UTC)

❌ Failed Tests (1) -- 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)	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 32s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	2m 1s	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 Tue, 04 Feb 2025 12:33:50 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	22.7 efps (44ms)	21.3 efps (47ms)	+3ms (+6.8%)	✅
article (body)	51.0 efps (20ms)	50.8 efps (20ms)	+0ms (+0.5%)	✅
article (string inside object)	23.8 efps (42ms)	22.2 efps (45ms)	+3ms (+7.1%)	✅
article (string inside array)	20.8 efps (48ms)	19.2 efps (52ms)	+4ms (+8.3%)	✅
recipe (name)	50.0 efps (20ms)	51.3 efps (20ms)	-1ms (-2.5%)	✅
recipe (description)	55.6 efps (18ms)	58.8 efps (17ms)	-1ms (-5.6%)	✅
recipe (instructions)	99.9+ efps (5ms)	99.9+ efps (6ms)	+1ms (-/-%)	✅
synthetic (title)	19.0 efps (53ms)	18.9 efps (53ms)	+1ms (+1.0%)	✅
synthetic (string inside object)	19.6 efps (51ms)	20.4 efps (49ms)	-2ms (-3.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)	44ms	71ms	111ms	475ms	1033ms	12.1s
article (body)	20ms	25ms	50ms	222ms	526ms	6.8s
article (string inside object)	42ms	45ms	52ms	255ms	528ms	7.7s
article (string inside array)	48ms	51ms	60ms	338ms	506ms	7.7s
recipe (name)	20ms	22ms	26ms	42ms	0ms	6.8s
recipe (description)	18ms	19ms	20ms	29ms	0ms	4.5s
recipe (instructions)	5ms	8ms	8ms	22ms	0ms	3.2s
synthetic (title)	53ms	55ms	58ms	80ms	489ms	12.0s
synthetic (string inside object)	51ms	59ms	69ms	448ms	1171ms	9.0s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	47ms	70ms	84ms	477ms	827ms	12.1s
article (body)	20ms	22ms	39ms	83ms	230ms	6.2s
article (string inside object)	45ms	51ms	55ms	187ms	315ms	7.8s
article (string inside array)	52ms	56ms	63ms	184ms	435ms	7.9s
recipe (name)	20ms	21ms	24ms	44ms	0ms	6.7s
recipe (description)	17ms	18ms	21ms	36ms	0ms	4.4s
recipe (instructions)	6ms	7ms	8ms	20ms	0ms	3.2s
synthetic (title)	53ms	55ms	57ms	299ms	752ms	13.0s
synthetic (string inside object)	49ms	51ms	65ms	465ms	676ms	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.