fix(deps): update dependency @sanity/insert-menu to v1.0.18

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sanity/insert-menu (source)	1.0.17 -> 1.0.18

---

Release Notes

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

v1.0.18

Bug Fixes

• remove direct @types/react dep (2d5ad4c)

---

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	Dec 23, 2024 0:22am
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 23, 2024 0:22am
test-next-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 23, 2024 0:22am
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 23, 2024 0:22am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Dec 23, 2024 0:22am

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/[email protected]	Transitive: environment	+2	7.6 MB	sanity-io

🚮 Removed packages: npm/@sanity/[email protected]

View full report↗︎

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Dec 23, 2024 12:18 AM (UTC)

✅ All Tests Passed -- 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	✅ Passed (Inspect)	39s	6	0	0
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 5s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	1m 26s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	1m 39s	18	0	0
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx	✅ Passed (Inspect)	12s	3	9	0
formBuilder/inputs/PortableText/Styles.spec.tsx	✅ Passed (Inspect)	26s	6	0	0
formBuilder/inputs/PortableText/Toolbar.spec.tsx	✅ Passed (Inspect)	1m 42s	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, 23 Dec 2024 00:20:49 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	27.8 efps (36ms)	25.6 efps (39ms)	+3ms (+8.3%)	✅
article (body)	68.0 efps (15ms)	67.1 efps (15ms)	+0ms (-/-%)	✅
article (string inside object)	26.3 efps (38ms)	26.3 efps (38ms)	+0ms (-/-%)	✅
article (string inside array)	25.6 efps (39ms)	24.4 efps (41ms)	+2ms (+5.1%)	✅
recipe (name)	52.6 efps (19ms)	55.6 efps (18ms)	-1ms (-5.3%)	✅
recipe (description)	62.5 efps (16ms)	62.5 efps (16ms)	+0ms (-/-%)	✅
recipe (instructions)	99.9+ efps (5ms)	99.9+ efps (5ms)	-0ms (-/-%)	✅
synthetic (title)	18.2 efps (55ms)	19.6 efps (51ms)	-4ms (-7.3%)	✅
synthetic (string inside object)	19.6 efps (51ms)	20.0 efps (50ms)	-1ms (-2.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)	36ms	38ms	51ms	420ms	197ms	9.8s
article (body)	15ms	17ms	18ms	81ms	207ms	5.2s
article (string inside object)	38ms	45ms	51ms	165ms	174ms	6.7s
article (string inside array)	39ms	46ms	51ms	91ms	398ms	7.1s
recipe (name)	19ms	21ms	24ms	38ms	0ms	6.9s
recipe (description)	16ms	17ms	20ms	28ms	0ms	4.3s
recipe (instructions)	5ms	7ms	9ms	21ms	0ms	3.0s
synthetic (title)	55ms	58ms	65ms	266ms	682ms	13.8s
synthetic (string inside object)	51ms	57ms	88ms	501ms	1047ms	8.9s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	39ms	48ms	70ms	578ms	1071ms	11.3s
article (body)	15ms	17ms	21ms	56ms	94ms	5.1s
article (string inside object)	38ms	43ms	49ms	189ms	391ms	7.0s
article (string inside array)	41ms	45ms	57ms	259ms	267ms	7.0s
recipe (name)	18ms	20ms	22ms	51ms	1ms	6.8s
recipe (description)	16ms	18ms	27ms	35ms	0ms	4.4s
recipe (instructions)	5ms	6ms	7ms	20ms	0ms	3.0s
synthetic (title)	51ms	54ms	61ms	260ms	545ms	13.0s
synthetic (string inside object)	50ms	52ms	63ms	539ms	557ms	8.3s

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