Skip to content

chore(deps): update app dependencies to v5 - #1781

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-5-app-dependencies
Open

chore(deps): update app dependencies to v5#1781
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-5-app-dependencies

Conversation

@renovate

@renovate renovate Bot commented Jan 26, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@sanity/icons (source) 3.7.45.2.1 age confidence
@sanity/vercel-protection-bypass (source) 2.0.15.0.19 age confidence
@sanity/vision (source) 4.6.15.31.1 age confidence
@sanity/visual-editing (source) 3.0.45.7.3 age confidence
groq (source) 4.6.15.31.1 age confidence
sanity (source) 4.6.15.31.1 age confidence
sanity-plugin-iframe-pane (source) 4.0.05.0.30 age confidence

Release Notes

sanity-io/ui (@​sanity/icons)

v5.2.1

Patch Changes

v5.2.0

Minor Changes
  • #​234 6dae460 Thanks @​stipsan! - Restore React 18 support.

    Icon components (and the Icon wrapper) are wrapped in React.forwardRef again, so refs attach to the underlying svg element on React 18 as well as React 19. The react peer dependency range is widened from ^19 to ^18 || ^19, and the Node.js engines range from >=22.12 to >=20.19 <22 || >=22.12, matching @sanity/ui.

v5.1.0

Minor Changes
  • #​223 e5657d5 Thanks @​stipsan! - Importing an icon from the root entry now resolves in the type system to a @deprecated never-typed tombstone instead of failing with a bare "has no exported member" error. Since v5 removed the per-icon barrel exports, import {RocketIcon} from '@sanity/icons' was indistinguishable from the icon having been deleted; the tombstone's deprecation message now points at the subpath the icon lives on, e.g. import {RocketIcon} from '@sanity/icons/Rocket'. The tombstones are declaration-only (export declare const RocketIcon: never), so nothing changes at runtime: the root entry still ships no icon code and bundlers/Node.js still reject root icon imports.

v5.0.0

Major Changes
  • #​215 19689cc Thanks @​stipsan! - The deprecated per-icon barrel exports are removed: import {RocketIcon} from '@sanity/icons' no longer works, import icons from their own export path instead, e.g. import {RocketIcon} from '@sanity/icons/Rocket'. The root entry now only exposes the dynamic pieces – the <Icon> component, the icons map, and their types – and every entry in the icons map is built with React.lazy, so importing the root entry no longer pulls the full icon set into your bundle: each icon loads as its own chunk the first time it renders. <Icon> wraps the lazy icon in a <Suspense> boundary whose fallback is an svg with the same shell (viewBox, width/height and spread props) as the icon it is loading, so the slot reserves its final size and responds to the same styling while the chunk loads – the way an <img> with intrinsic dimensions behaves. When rendering components from the icons map directly, provide your own <Suspense> boundary.

v4.1.0

Minor Changes
  • #​182 e7538d4 Thanks @​stipsan! - Every icon is now available on its own export path, e.g. import {RocketIcon} from '@sanity/icons/Rocket', letting userland opt in to smaller bundles and faster treeshaking. Each subpath exposes the icon both as a named export (identical to the barrel export) and as the default export, so React.lazy(() => import('@sanity/icons/Rocket')) works out of the box. Importing individual icons from the root barrel (import {RocketIcon} from '@sanity/icons') still works but is now marked @deprecated, pointing to the per-icon subpath to avoid barrel file performance issues.

v4.0.0

Major Changes
  • #​200 26b9248 Thanks @​stipsan! - Drop CommonJS support and require Node.js >=22.12

    @sanity/icons is now ESM-only. The require export condition and the CommonJS build output (./dist/index.cjs) have been removed, so the package must be consumed via ESM import. The minimum supported Node.js version has been raised to >=22.12 to match sanity.

  • #​201 01e3807 Thanks @​stipsan! - Drop React 18 support — React 19 is now required.

    Icon components no longer use forwardRef. Refs are now accepted as a regular prop (typed via React.ComponentPropsWithRef), following React 19's ref-as-prop model. The react peer dependency range is now ^19, and the exported IconComponent type has changed accordingly.

v3.8.0

Minor Changes
Patch Changes

v3.7.7

Patch Changes
  • #​181 5b9d2cb Thanks @​stipsan! - Bumped @testing-library/react, @types/node, and @types/react devDependencies to their latest versions.

v3.7.6

Bug Fixes
  • enable trusted publishing (925545b)
sanity-io/plugins (@​sanity/vercel-protection-bypass)

v5.0.19

Compare Source

Patch Changes

v5.0.18

Compare Source

Patch Changes

v5.0.17

Compare Source

Patch Changes

v5.0.16

Compare Source

Patch Changes

v5.0.15

Compare Source

Patch Changes

v5.0.14

Compare Source

Patch Changes

v5.0.13

Compare Source

Patch Changes
  • #​1491 2361892 Thanks @​stipsan! - Build with tsdown instead of @sanity/pkg-utils. Internal build-tooling change only, with no intended changes to the public API or runtime behavior.

v5.0.12

Patch Changes
  • #​1460 f50f060 Thanks @​stipsan! - Regenerate TypeScript declaration output: isolatedDeclarations is no longer used and declarations are now generated with tsgo (@typescript/native-preview). Internal build-tooling change only, with no runtime behavior or public API changes.

v5.0.11

Patch Changes
  • #​1471 52487d2 Thanks @​stipsan! - Update @sanity/icons to v4 and adopt its per-icon import paths for smaller bundles and faster treeshaking

v5.0.10

Compare Source

Patch Changes

v5.0.9

Compare Source

Patch Changes

v5.0.8

Compare Source

Patch Changes
  • #​903 2f03c8d Thanks @​bjoerge! - Widen sanity peer-dependency range to ^5 || ^6.0.0-0 to support Sanity Studio v6 (including v6 pre-releases).

v5.0.7

Compare Source

Patch Changes

v5.0.6

Compare Source

Patch Changes

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes

v4.0.6

Compare Source

Patch Changes

v4.0.5

Compare Source

Patch Changes

v4.0.4

Compare Source

Patch Changes

v4.0.3

Compare Source

Patch Changes

v4.0.2

Compare Source

Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes

v3.1.0

Compare Source

Minor Changes
Patch Changes

v3.0.0

Compare Source

Major Changes
Patch Changes

v2.1.1

Patch Changes

v2.1.0

Features

v2.0.2

Dependencies
sanity-io/sanity (@​sanity/vision)

v5.31.1

Compare Source

Sanity Studio v5.31.1

For the complete changelog with all details, please visit:
www.sanity.io/docs/changelog/5e41ca5a-489c-4390-a9e8-f3712b30bf37

Install or upgrade Sanity Studio

To upgrade to this version, run:

npm install sanity@latest

To initiate a new Sanity Studio project or learn more about upgrading, please refer to our comprehensive guide on Installing and Upgrading Sanity Studio.

📓 Full changelog

Author Message Commit
@​stipsan fix(core): revert use schema preview selection for search (#​13029) ec87ab7
@​stipsan fix(core): exclude dereference paths from groq2024 score boosts (#​13027) ca4657e
@​bjoerge ci(release): add commit log and working compare link to v5 release pr (#​13028) 75a443d
@​bjoerge ci(release): block v5 release pr when commits would cause a major bump 0b8f8e3
@​bjoerge ci(release): keep pnpm install output out of v5 release pr description 451b07b
@​bjoerge chore(ci): set up release automation for v5 65d0a0c
squiggler-app[bot] chore(release): publish v5.31.1 (#​13022) 1cd4e22

v5.31.0

Compare Source

Features
Bug Fixes

v5.30.0

Compare Source

Sanity Studio v5.30.0

This release includes various improvements and bug fixes.

For the complete changelog with all details, please visit:
www.sanity.io/changelog/studio-NS4yOS4w

Install or upgrade Sanity Studio

To upgrade to this version, run:

npm install sanity@latest

To initiate a new Sanity Studio project or learn more about upgrading, please refer to our comprehensive guide on Installing and Upgrading Sanity Studio.

📓 Full changelog
Author Message Commit
@​bjoerge fix(authStore): resolve dual-mode SSO login loop (#​12933) 2ae1370
@​bjoerge feat: add vercel routing configuration for auth-test-studio (#​12929) cf5baeb
squiggler-app[bot] fix(deps): update dependency @​sanity/cli to ^6.7.1 (#​12928) df8fc74

v5.29.0

Compare Source

Sanity Studio v5.29.0

This release includes various improvements and bug fixes.

For the complete changelog with all details, please visit:
www.sanity.io/changelog/studio-NS4yOC4w

Install or upgrade Sanity Studio

To upgrade to this version, run:

npm install sanity@latest

To initiate a new Sanity Studio project or learn more about upgrading, please refer to our comprehensive guide on Installing and Upgrading Sanity Studio.

📓 Full changelog

Author Message Commit
squiggler-app[bot] fix(deps): update dependency @​sanity/cli to ^6.7.0 (#​12924) 3fa8dc5
@​bjoerge fix(core): respect parent array field initialValue over member fields (#​12914) 46f9caa
@​pedrobonamin fix(structure): memoize incoming refs filter (#​12919) 30f89d5
sieve-sanity[bot] fix(sanity): surface error when no uploader matches the file (#​12870) (#​12905) 054950f
@​pedrobonamin chore(e2e): add variants e2e tests and readme (#​12866) 3a2fc8b
@​juice49 fix(sanity): incorrect form auto-focus (#​12878) 8df5ed3
squiggler-app[bot] chore(deps): dedupe pnpm-lock.yaml (#​12874) 00aa753
@​pedrobonamin chore(core): add variants conditions autocomplete (#​12858) 07d4dd9
@​pedrobonamin chore(core): update variants operation store to use system actions (#​12915) 472c314
@​pedrobonamin feat(core): add variant definition edit form (#​12855) 21c6530
squiggler-app[bot] chore(deps): update dependency @​sanity/pkg-utils to ^10.5.1 (#​12900) daf6c35
@​bjoerge fix(form): revert dataset aclMode check for plain asset previews (#​12913) 34982cf
squiggler-app[bot] chore(deps): update dependency @​sanity/blueprints to ^0.19.1 (#​12889) 4c3064b
squiggler-app[bot] chore(deps): update playwright monorepo to v1.60.0 (#​12912) 2273ad6
@​juice49 fix(sanity): restore document form open path from URL (#​12873) 07cda46
@​geball chore: fix typo (#​12906) 65872fe

v5.28.0

Compare Source

Sanity Studio v5.28.0

This release includes various improvements and bug fixes.

For the complete changelog with all details, please visit:
www.sanity.io/changelog/studio-NS4yNy4w

Install or upgrade Sanity Studio

To upgrade to this version, run:

npm install sanity@latest

To initiate a new Sanity Studio project or learn more about upgrading, please refer to our comprehensive guide on Installing and Upgrading Sanity Studio.

📓 Full changelog

Author Message Commit
@​stipsan fix(presentation): handle null client.fetch results in PostMessageSchema (#​12904) 4397d7b
@​stipsan fix(presentation): avoid iframe reload on perspective switch (#​12885) 1b76d8b
@​stipsan fix(presentation): handle agent bundle perspectives correctly (#​12903) a91bdc2
squiggler-app[bot] fix(deps): update dependency @​sanity/insert-menu to v3.0.7 (#​12897) 9dea35a
squiggler-app[bot] chore(deps): update dependency @​sanity/visual-editing-csm to ^3.0.8 (#​12895) 5c460ed
squiggler-app[bot] fix(deps): update dependency @​sanity/preview-url-secret to ^4.0.6 (#​12898) 931641a
squiggler-app[bot] fix(deps): Update dev-non-major (#​12888) 632282c
@​jordanl17 refactor(telemetry): replace PTE fullscreen events with Editor Opened/Closed + properties (#​12883) 6195111
squiggler-app[bot] fix(deps): update dependency @​sanity/presentation-comlink to ^2.1.0 (#​12881) e604c3e
squiggler-app[bot] fix(deps): update dependency @​sanity/client to ^7.22.0 (#​12880) 8a5b3ae
@​jordanl17 refactor(telemetry): rename Canvas Opened from studio event to Canvas Opened (#​12884) e16ba95
squiggler-app[bot] chore(deps): update dev-non-major (#​12579) c4b5b4d
@​pedrobonamin feat(core): add view-as navbar for variant selection (#​12862) 4b5e4bb

v5.27.0

Compare Source

Sanity Studio v5.27.0

This release includes various improvements and bug fixes.

For the complete changelog with all details, please visit:
www.sanity.io/changelog/studio-NS4yNi4w

Install or upgrade Sanity Studio

To upgrade to this version, run:

npm install sanity@latest

To initiate a new Sanity Studio project or learn more about upgrading, please refer to our comprehensive guide on Installing and Upgrading Sanity Studio.

📓 Full changelog

Author Message Commit
squiggler-app[bot] chore(deps): dedupe pnpm-lock.yaml (#​12846) 2057560
@​juice49 fix(sanity): add SanityImageSource to permitted media preview types (#​12863) ecf8f39
@​juice49 fix(sanity): set correct dimensions for PTE block image preview (#​12863) 44bc72c
@​pedrobonamin feat(actions): adds sieve (#​12864) 5742d89
@​bjoerge chore(ci): add node 26 to test matrix (#​12860) ca41e8f
@​juice49 fix(sanity): full-screen PTE popover boundaries (#​12857) c78ec37
@​pedrobonamin feat(core): add variant definition delete action (#​12848) e296b6c
@​pedrobonamin feat(core): initial implementation for variants creation form (#​12847) 9178fe2
@​pedrobonamin feat(core): Setting up variants tool (#​12840) ee6c149
@​pedrobonamin fix(i18n): mark stable resources for translation (#​12861) 36a8b11
@​bjoerge chore(ci): bring back build metadata for prereleases (#​12856) 2428346
@​hermanwikner fix(comments): hide empty field wrapper when field component is hidden ([#​12773](https://redirect.github.com/sanity-io/sanity/issues/12773

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 3am on Monday"
  • 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 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 Sanity. View repository job log here

@vercel

vercel Bot commented Jan 26, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
preview-kit-next-app-router Ready Ready Preview Aug 4, 2026 8:07pm
preview-kit-next-pages-router Error Error Aug 4, 2026 8:07pm
preview-kit-remix Error Error Aug 4, 2026 8:07pm
preview-kit-test-studio Error Error Aug 4, 2026 8:07pm

Request Review

@socket-security

socket-security Bot commented Jan 26, 2026

Copy link
Copy Markdown

@socket-security

socket-security Bot commented Jan 26, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @vercel/stega is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/[email protected]npm/@sanity/[email protected]npm/@vercel/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: 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 [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vercel/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm data-urls is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/[email protected]npm/[email protected]npm/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: 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 [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm jsdom is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/[email protected]npm/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: 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 [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm jsdom is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/[email protected]npm/[email protected]npm/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: 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 [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm web-vitals is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/[email protected]npm/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: 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 [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate
renovate Bot force-pushed the renovate/major-5-app-dependencies branch from 5d159e4 to 8c59c5f Compare January 27, 2026 16:31
@renovate
renovate Bot force-pushed the renovate/major-5-app-dependencies branch from 8c59c5f to 5f65a7d Compare January 29, 2026 13:03
@renovate
renovate Bot force-pushed the renovate/major-5-app-dependencies branch from 5f65a7d to 2a0578a Compare January 30, 2026 18:54
@renovate
renovate Bot force-pushed the renovate/major-5-app-dependencies branch from 2a0578a to 6b3d417 Compare February 2, 2026 16:36
@renovate
renovate Bot force-pushed the renovate/major-5-app-dependencies branch from b9fba09 to 53eeb47 Compare February 5, 2026 16:52
@renovate
renovate Bot force-pushed the renovate/major-5-app-dependencies branch from 53eeb47 to fa996c9 Compare February 6, 2026 02:44
@renovate
renovate Bot force-pushed the renovate/major-5-app-dependencies branch from fa996c9 to 626a47c Compare February 6, 2026 14:52
@renovate
renovate Bot force-pushed the renovate/major-5-app-dependencies branch from 626a47c to 024e209 Compare February 10, 2026 16:05
@renovate
renovate Bot force-pushed the renovate/major-5-app-dependencies branch from 024e209 to 5f26837 Compare February 12, 2026 14:51
@renovate
renovate Bot force-pushed the renovate/major-5-app-dependencies branch from 5f26837 to 4a1ef2b Compare February 15, 2026 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants