fix(deps): update dependency @sanity/client to ^6.27.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sanity/client (source)	^6.25.0 -> ^6.27.0

---

Release Notes

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

v6.27.0

Compare Source

Features

• csm: support releases in applySourceDocuments (#​981) (ab82a35)

---

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)			Jan 22, 2025 4:00pm
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 22, 2025 4:00pm
test-studio	🛑 Canceled (Inspect)			Jan 22, 2025 4:00pm

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Jan 22, 2025 4:00pm
test-next-studio	⬜️ Ignored (Inspect)			Jan 22, 2025 4:00pm

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/[email protected] 🔁 npm/@sanity/[email protected]	None	0	0 B

View full report↗︎

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Jan 22, 2025 4:23 PM (UTC)

❌ Failed Tests (2) -- 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 33s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	❌ Failed (Inspect)	2m 42s	20	0	1
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 Wed, 22 Jan 2025 16:33:42 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	27.0 efps (37ms)	25.6 efps (39ms)	+2ms (+5.4%)	✅
article (body)	63.1 efps (16ms)	63.3 efps (16ms)	-0ms (-/-%)	✅
article (string inside object)	27.0 efps (37ms)	27.0 efps (37ms)	+0ms (-/-%)	✅
article (string inside array)	23.0 efps (44ms)	23.3 efps (43ms)	-1ms (-1.1%)	✅
recipe (name)	47.6 efps (21ms)	50.0 efps (20ms)	-1ms (-4.8%)	✅
recipe (description)	55.6 efps (18ms)	55.6 efps (18ms)	+0ms (-/-%)	✅
recipe (instructions)	99.9+ efps (6ms)	99.9+ efps (5ms)	-1ms (-/-%)	✅
synthetic (title)	18.9 efps (53ms)	17.2 efps (58ms)	+5ms (+9.4%)	✅
synthetic (string inside object)	19.6 efps (51ms)	18.5 efps (54ms)	+3ms (+5.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)	37ms	42ms	54ms	485ms	344ms	10.8s
article (body)	16ms	19ms	52ms	249ms	455ms	6.2s
article (string inside object)	37ms	39ms	44ms	249ms	261ms	6.7s
article (string inside array)	44ms	46ms	53ms	77ms	147ms	6.9s
recipe (name)	21ms	24ms	29ms	42ms	0ms	7.2s
recipe (description)	18ms	19ms	20ms	37ms	0ms	4.4s
recipe (instructions)	6ms	8ms	9ms	28ms	0ms	3.2s
synthetic (title)	53ms	55ms	70ms	414ms	999ms	13.4s
synthetic (string inside object)	51ms	53ms	60ms	297ms	815ms	8.9s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	39ms	47ms	75ms	460ms	920ms	11.1s
article (body)	16ms	19ms	28ms	198ms	266ms	5.5s
article (string inside object)	37ms	40ms	43ms	177ms	165ms	6.7s
article (string inside array)	43ms	48ms	68ms	244ms	319ms	7.3s
recipe (name)	20ms	22ms	25ms	33ms	0ms	7.7s
recipe (description)	18ms	20ms	24ms	32ms	0ms	4.7s
recipe (instructions)	5ms	6ms	7ms	16ms	0ms	3.1s
synthetic (title)	58ms	64ms	79ms	197ms	1346ms	13.4s
synthetic (string inside object)	54ms	57ms	67ms	718ms	1818ms	9.6s

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