chore(deps): update dependency sanity to v3.41.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
sanity (source)	3.41.0 -> 3.41.1

---

Release Notes

sanity-io/sanity (sanity)

v3.41.1

Compare Source

Installation and upgrading

To initiate a new Studio without installing the CLI globally:

npm create sanity@latest

To upgrade a v3 Studio, run this command in its folder:

npm install sanity@latest

🐛 Notable bugfixes

• Fixes a regression in Presentation Tool introduced in v3.41.0 that causes it to crash in embedded studios.

📓 Full changelog

Author | Message | Commit
------------ | ------------- | -------------
Binoy Patel | test(core): fixes flaky test with document publish (#​6595) | 2a8375a
renovate[bot] | chore(deps): update linters (#​6590) | 59b8ce8
renovate[bot] | chore(deps): update dependency styled-components to ^6.1.10 (#​6585) | 5e727e0
renovate[bot] | chore(lockfile): update dependency zod to v3.23.7 (#​6527) | 571dd56
renovate[bot] | chore(deps): update dependency @​sanity/pkg-utils to v6.8.13 (#​6599) | d9f9188
renovate[bot] | chore(deps): update dependency @​sanity/tsdoc to v1.0.51 (#​6600) | 56a8a79
renovate[bot] | chore(lockfile): update dependency @​sanity/react-loader to v1.9.17 (#​6584) | 0819c40
Cody Olsen | fix(presentation): regression causing a crash when in an embedded studio (#​6606) | 99dfb60

---

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 becomes conflicted, 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

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sanity/[email protected]	environment Transitive: eval, filesystem, shell, unsafe	+62	49.2 MB	sanity-io
npm/@sanity/[email protected]	Transitive: filesystem	+4	93.7 kB	sanity-io
npm/@sanity/[email protected]	environment Transitive: filesystem	+8	7.18 MB	sanity-io
npm/@types/[email protected]	None	+2	250 kB	types
npm/@types/[email protected]	None	+1	42.5 kB	types
npm/@types/[email protected]	None	0	73.6 kB	types
npm/@types/[email protected]	None	0	1.97 MB	types
npm/@types/[email protected]	None	0	8.76 kB	types

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
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	orphan: npm/[email protected]

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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]

[stipsan]

@SocketSecurity ignore npm/[email protected]