chore(deps): update dependency @sanity/tsdoc to v1.0.53

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sanity/tsdoc (source)	1.0.51 -> 1.0.53

---

Release Notes

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

v1.0.53

Compare Source

Bug Fixes

• deps: update dependency @​sanity/pkg-utils to v6.8.14 (#​209) (feef429)

v1.0.52

Compare Source

Bug Fixes

• deps: update dependency @​microsoft/api-extractor to v7.43.4 (#​205) (65509e2)
• deps: update dependency @​microsoft/api-extractor-model to v7.28.16 (#​206) (dd8636d)
• deps: update dependency @​sanity/ui to ^2.1.7 (#​207) (cd97dd6)
• deps: update dependency esbuild to ^0.21.2 (#​208) (4b19ef8)
• deps: Update sanity monorepo (#​204) (fff813b)

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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)
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 14, 2024 10:09am
test-next-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 14, 2024 10:09am
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 14, 2024 10:09am

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		May 14, 2024 10:09am

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated May 14, 2024 10:08 AM (UTC)

File	Status	Duration	Passed	Skipped	Failed
comments/CommentInput.spec.tsx	✅ Passed (Inspect)	35s	15	0	0
formBuilder/ArrayInput.spec.tsx	✅ Passed (Inspect)	6s	3	0	0
formBuilder/inputs/PortableText/Annotations.spec.tsx	✅ Passed (Inspect)	26s	6	0	0
formBuilder/inputs/PortableText/copyPaste/CopyPaste.spec.tsx	✅ Passed (Inspect)	31s	11	7	0
formBuilder/inputs/PortableText/Decorators.spec.tsx	✅ Passed (Inspect)	14s	6	0	0
formBuilder/inputs/PortableText/FocusTracking.spec.tsx	✅ Passed (Inspect)	35s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	1m 6s	14	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	1m 5s	18	0	0
formBuilder/inputs/PortableText/PresenceCursors.spec.tsx	✅ Passed (Inspect)	7s	3	9	0
formBuilder/inputs/PortableText/RangeDecoration.spec.tsx	✅ Passed (Inspect)	20s	9	0	0
formBuilder/inputs/PortableText/Styles.spec.tsx	✅ Passed (Inspect)	14s	6	0	0
formBuilder/inputs/PortableText/Toolbar.spec.tsx	✅ Passed (Inspect)	22s	9	0	0

[stipsan]

Like #6630, mostly bugfixes in underlying packages like esbuild, recast and @microsoft/api-extractor in this one

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/tsdoc@1.0.53	Transitive: environment, filesystem, shell, unsafe	+22	14.3 MB
npm/@vercel/frameworks@1.6.0	filesystem Transitive: eval	+1	312 kB	vercel-release-bot
npm/@vercel/fs-detectors@4.1.3	environment, filesystem, shell	+2	277 kB	vercel-release-bot
npm/@vercel/stega@0.1.2	None	0	29.4 kB	vercel-release-bot
npm/@vitejs/plugin-react@4.2.1	None	+2	52.4 kB	vitebot
npm/@vvo/tzdb@6.137.0	None	0	175 kB	vvo

🚮 Removed packages: npm/@sanity/tsdoc@1.0.51

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/core-js@2.6.12

View full report↗︎

Next steps

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[stipsan]

@SocketSecurity ignore npm/core-js@2.6.12