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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v2.8.24

Compare Source

Bug Fixes

• deps: update React Compiler dependencies 🤖 ✨ (#​1474) (52ce554)

---

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	🛑 Canceled (Inspect)			Nov 19, 2024 0:32am
performance-studio	🛑 Canceled (Inspect)		💬 Add feedback	Nov 19, 2024 0:32am
test-compiled-studio	🛑 Canceled (Inspect)			Nov 19, 2024 0:32am
test-next-studio	🛑 Canceled (Inspect)			Nov 19, 2024 0:32am
test-studio	🛑 Canceled (Inspect)			Nov 19, 2024 0:32am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Nov 19, 2024 0:32am

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/ui@2.8.24	Transitive: environment	+27	17 MB	sanity-io

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

View full report↗︎

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Nov 19, 2024 12:01 AM (UTC)

❌ Failed Tests (2) -- expand for details

File	Status	Duration	Passed	Skipped	Failed
comments/CommentInput.spec.tsx	✅ Passed (Inspect)	48s	15	0	0
formBuilder/ArrayInput.spec.tsx	✅ Passed (Inspect)	9s	3	0	0
formBuilder/inputs/PortableText/Annotations.spec.tsx	✅ Passed (Inspect)	32s	6	0	0
formBuilder/inputs/PortableText/copyPaste/CopyPaste.spec.tsx	❌ Failed (Inspect)	58s	9	7	2
formBuilder/inputs/PortableText/copyPaste/CopyPasteFields.spec.tsx	✅ Passed (Inspect)	0s	0	12	0
formBuilder/inputs/PortableText/Decorators.spec.tsx	✅ Passed (Inspect)	17s	6	0	0
formBuilder/inputs/PortableText/DisableFocusAndUnset.spec.tsx	✅ Passed (Inspect)	11s	3	0	0
formBuilder/inputs/PortableText/DragAndDrop.spec.tsx	✅ Passed (Inspect)	3m 0s	0	0	0
formBuilder/inputs/PortableText/FocusTracking.spec.tsx	✅ Passed (Inspect)	46s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	1m 46s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	1m 16s	18	0	0
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx	✅ Passed (Inspect)	9s	3	9	0
formBuilder/inputs/PortableText/RangeDecoration.spec.tsx	✅ Passed (Inspect)	27s	9	0	0
formBuilder/inputs/PortableText/Styles.spec.tsx	✅ Passed (Inspect)	18s	6	0	0
formBuilder/inputs/PortableText/Toolbar.spec.tsx	✅ Passed (Inspect)	37s	12	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, 19 Nov 2024 00:00:07 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	17.5 efps (57ms)	18.7 efps (54ms)	-4ms (-6.1%)	✅
article (body)	63.7 efps (16ms)	56.5 efps (18ms)	+2ms (+12.7%)	✅
article (string inside object)	18.5 efps (54ms)	20.0 efps (50ms)	-4ms (-7.4%)	✅
article (string inside array)	16.1 efps (62ms)	16.1 efps (62ms)	+0ms (-/-%)	✅
recipe (name)	30.3 efps (33ms)	31.3 efps (32ms)	-1ms (-3.0%)	✅
recipe (description)	34.5 efps (29ms)	35.7 efps (28ms)	-1ms (-3.4%)	✅
recipe (instructions)	99.9+ efps (6ms)	99.9+ efps (6ms)	+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)	57ms	64ms	73ms	228ms	433ms	13.2s
article (body)	16ms	18ms	24ms	190ms	284ms	5.9s
article (string inside object)	54ms	57ms	60ms	226ms	274ms	8.7s
article (string inside array)	62ms	68ms	88ms	292ms	859ms	9.3s
recipe (name)	33ms	37ms	58ms	88ms	25ms	8.8s
recipe (description)	29ms	31ms	35ms	56ms	0ms	5.8s
recipe (instructions)	6ms	7ms	8ms	9ms	0ms	3.3s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	54ms	60ms	71ms	294ms	483ms	13.2s
article (body)	18ms	22ms	38ms	111ms	284ms	5.7s
article (string inside object)	50ms	53ms	56ms	75ms	75ms	7.7s
article (string inside array)	62ms	66ms	77ms	296ms	865ms	9.3s
recipe (name)	32ms	35ms	55ms	90ms	0ms	8.6s
recipe (description)	28ms	30ms	34ms	48ms	0ms	5.7s
recipe (instructions)	6ms	8ms	9ms	11ms	0ms	3.2s

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