fix(deps): update dependency react-rx to ^4.1.11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-rx (source)	^4.1.10 -> ^4.1.11

---

Release Notes

sanity-io/react-rx (react-rx)

v4.1.11

Compare Source

Bug Fixes

• deps: update React Compiler dependencies 🤖 ✨ (#​191) (b917280)

---

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

1 Skipped Deployment

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

[socket-security]

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

🚮 Removed packages: npm/[email protected]

View full report↗︎

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Dec 31, 2024 12:51 PM (UTC)

❌ Failed Tests (1) -- expand for details

File	Status	Duration	Passed	Skipped	Failed
comments/CommentInput.spec.tsx	✅ Passed (Inspect)	1m 6s	15	0	0
formBuilder/ArrayInput.spec.tsx	✅ Passed (Inspect)	12s	3	0	0
formBuilder/inputs/PortableText/Annotations.spec.tsx	❌ Failed (Inspect)	1m 18s	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 5s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	1m 27s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	1m 38s	18	0	0
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx	✅ Passed (Inspect)	12s	3	9	0
formBuilder/inputs/PortableText/Styles.spec.tsx	✅ Passed (Inspect)	25s	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 Tue, 31 Dec 2024 12:53:20 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	28.2 efps (36ms)	28.6 efps (35ms)	-1ms (-1.4%)	✅
article (body)	72.7 efps (14ms)	75.2 efps (13ms)	-0ms (-/-%)	✅
article (string inside object)	26.3 efps (38ms)	29.0 efps (35ms)	-4ms (-9.2%)	✅
article (string inside array)	25.0 efps (40ms)	26.3 efps (38ms)	-2ms (-5.0%)	✅
recipe (name)	52.6 efps (19ms)	58.8 efps (17ms)	-2ms (-10.5%)	✅
recipe (description)	58.8 efps (17ms)	64.5 efps (16ms)	-2ms (-8.8%)	✅
recipe (instructions)	99.9+ efps (5ms)	99.9+ efps (5ms)	+0ms (-/-%)	✅
synthetic (title)	18.5 efps (54ms)	19.6 efps (51ms)	-3ms (-5.6%)	✅
synthetic (string inside object)	18.7 efps (54ms)	18.9 efps (53ms)	-1ms (-0.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)	36ms	39ms	50ms	238ms	234ms	10.3s
article (body)	14ms	16ms	17ms	42ms	61ms	4.6s
article (string inside object)	38ms	40ms	59ms	170ms	161ms	6.7s
article (string inside array)	40ms	42ms	49ms	177ms	135ms	6.7s
recipe (name)	19ms	20ms	25ms	44ms	0ms	8.4s
recipe (description)	17ms	18ms	21ms	34ms	0ms	4.4s
recipe (instructions)	5ms	7ms	10ms	20ms	0ms	3.1s
synthetic (title)	54ms	58ms	64ms	278ms	661ms	14.1s
synthetic (string inside object)	54ms	58ms	95ms	485ms	898ms	8.5s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	35ms	40ms	51ms	371ms	178ms	9.8s
article (body)	13ms	16ms	18ms	86ms	57ms	4.8s
article (string inside object)	35ms	38ms	48ms	91ms	129ms	6.4s
article (string inside array)	38ms	40ms	43ms	88ms	140ms	6.5s
recipe (name)	17ms	18ms	20ms	37ms	0ms	8.0s
recipe (description)	16ms	17ms	19ms	34ms	0ms	4.3s
recipe (instructions)	5ms	7ms	9ms	27ms	0ms	3.0s
synthetic (title)	51ms	54ms	61ms	301ms	639ms	13.7s
synthetic (string inside object)	53ms	58ms	79ms	463ms	997ms	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.