fix(deps): Update dependency @sanity/pkg-utils to v6.8.15

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sanity/pkg-utils	6.8.14 -> 6.8.15

---

Release Notes

sanity-io/pkg-utils (@​sanity/pkg-utils)

v6.8.15

Compare Source

Bug Fixes

• only enable minifyInternalExports by default when minify: true (#​878) (ee50f48)

---

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (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/@rexxars/[email protected]	None	0	468 kB	rexxars
npm/@sanity/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+86	275 MB
npm/@sanity/[email protected]	Transitive: filesystem	+4	93.7 kB	sanity-io
npm/@sanity/[email protected]	environment Transitive: filesystem, unsafe	+48	15.5 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	+1	77 kB	types
npm/@types/[email protected]	None	0	1.97 MB	types
npm/@types/[email protected]	None	0	8.76 kB	types
npm/@types/[email protected]	None	0	35 kB	types
npm/@typescript-eslint/[email protected]	Transitive: environment	+10	5.75 MB	jameshenry
npm/@typescript-eslint/[email protected]	Transitive: environment	+6	1.83 MB	jameshenry

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/[email protected], npm/[email protected]

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

[stipsan]

@SocketSecurity ignore npm/[email protected]

[stipsan]

@SocketSecurity ignore npm/[email protected]