chore: merge next into corel

[jordanl17]

Description

What to review

Testing

Notes for release

[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 25, 2024 2:09am
performance-studio	✅ Ready (Inspect)	Visit Preview		Dec 25, 2024 2:09am
test-next-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 25, 2024 2:09am
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 25, 2024 2:09am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Dec 25, 2024 2:09am

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@portabletext/[email protected]	None	+7	10.4 MB	bjoerge, kmelve, mariuslundgard, ...6 more
npm/@sanity/[email protected]	Transitive: environment, eval	+9	8.39 MB	sanity-io
npm/@sanity/[email protected]	Transitive: environment	+2	7.6 MB	sanity-io
npm/@sanity/[email protected]	Transitive: network	+4	4.36 MB	armandocerna, ash, atombender, ...62 more
npm/@sanity/[email protected]	network Transitive: environment, filesystem, shell, unsafe	+24	13 MB	sanity-io
npm/@sanity/[email protected]	Transitive: eval, network	+7	14.6 MB	sanity-io
npm/@types/[email protected]	None	+1	447 kB	types
npm/[email protected]	environment, filesystem, network, shell, unsafe	+8	88 MB	vercel-release-bot

🚮 Removed packages: npm/@codemirror/[email protected], npm/@portabletext/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
License Policy Violation	npm/[email protected]	License: CC-BY-SA-4.0 - Not allowed by license policy (package/dist/compiled/glob/LICENSE, package/dist/compiled/glob/LICENSE)	dev/starter-next-studio/package.json pnpm-lock.yaml	⚠︎

View full report↗︎

Next steps

What is a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Dec 25, 2024 2:05 AM (UTC)

✅ All Tests Passed -- expand for details

File	Status	Duration	Passed	Skipped	Failed
comments/CommentInput.spec.tsx	✅ Passed (Inspect)	1m 7s	15	0	0
formBuilder/ArrayInput.spec.tsx	✅ Passed (Inspect)	13s	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 6s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	1m 28s	21	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	1m 39s	18	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 Wed, 25 Dec 2024 02:08:00 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	25.0 efps (40ms)	17.9 efps (56ms)	+16ms (+40.0%)	🔴
article (body)	63.1 efps (16ms)	58.0 efps (17ms)	+1ms (+8.8%)	✅
article (string inside object)	25.6 efps (39ms)	18.9 efps (53ms)	+14ms (+35.9%)	🔴
article (string inside array)	22.7 efps (44ms)	18.0 efps (56ms)	+12ms (+26.1%)	🔴
recipe (name)	55.6 efps (18ms)	33.3 efps (30ms)	+12ms (+66.7%)	🔴
recipe (description)	62.5 efps (16ms)	35.7 efps (28ms)	+12ms (+75.0%)	🔴
recipe (instructions)	99.9+ efps (5ms)	99.9+ efps (5ms)	+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)	40ms	44ms	55ms	392ms	209ms	11.0s
article (body)	16ms	18ms	28ms	208ms	250ms	5.8s
article (string inside object)	39ms	40ms	56ms	184ms	175ms	7.0s
article (string inside array)	44ms	46ms	49ms	176ms	144ms	7.2s
recipe (name)	18ms	19ms	21ms	30ms	0ms	7.0s
recipe (description)	16ms	18ms	20ms	35ms	0ms	4.3s
recipe (instructions)	5ms	6ms	8ms	11ms	0ms	3.0s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	56ms	73ms	106ms	508ms	1638ms	13.1s
article (body)	17ms	20ms	38ms	97ms	406ms	6.1s
article (string inside object)	53ms	55ms	58ms	175ms	573ms	8.1s
article (string inside array)	56ms	61ms	73ms	338ms	1138ms	9.0s
recipe (name)	30ms	31ms	36ms	43ms	0ms	7.6s
recipe (description)	28ms	29ms	33ms	47ms	0ms	5.5s
recipe (instructions)	5ms	7ms	8ms	33ms	0ms	3.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.