Skip to content

fix(deps): update sanity-tooling#1558

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/sanity-tooling
Open

fix(deps): update sanity-tooling#1558
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/sanity-tooling

Conversation

@renovate

@renovate renovate Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@sanity/client (source) ^7.23.2^7.24.0 age confidence
@sanity/pkg-utils (source) ^11.0.9^11.0.13 age confidence
@sanity/runtime-cli ^17.1.0^17.2.0 age confidence
@sanity/schema (source) ^6.5.0^6.6.0 age confidence
@sanity/types (source) ^6.5.0^6.6.0 age confidence
@sanity/ui (source) ^3.3.5^3.4.3 age confidence
@sanity/vision (source) ^6.5.0^6.6.0 age confidence
sanity (source) ^6.5.0^6.6.0 age confidence

Release Notes

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

v7.24.0

Compare Source

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

v11.0.13

Compare Source

Patch Changes

v11.0.12

Compare Source

Patch Changes

v11.0.11

Compare Source

Patch Changes

v11.0.10

Compare Source

Patch Changes
sanity-io/runtime-cli (@​sanity/runtime-cli)

v17.2.0

Compare Source

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

v6.6.0

Compare Source

Bug Fixes
sanity-io/sanity (@​sanity/types)

v6.6.0

Compare Source

Features
  • variants: enable editing variant documents through the document form (#​13505) (46d84dc)
sanity-io/ui (@​sanity/ui)

v3.4.3

Compare Source

Patch Changes
  • #​2435 f3638b5 Thanks @​stipsan! - Remove the displayName assignments that followed every component definition. As top-level Component.displayName = '…' statements in the published dist they were side effects that pinned every component into consuming bundles, defeating tree-shaking of unused components (see sanity-io/visual-editing#3535 for the kind of workaround this forced downstream). They were also redundant: every component is declared as a named function (e.g. forwardRef(function Button(…) {…})), so React DevTools derives the exact same name from Function.name — the build now passes keepNames so those function names survive into the dist.

    If you profile or debug production builds with React DevTools and want component names to survive your own app's minification, configure the bundler to keep identifier names instead of relying on displayName, e.g. in Vite:

    export default defineConfig({
      // Allows running React Profiler and better debugging
      resolve: {
        alias: { "react-dom/client": require.resolve("react-dom/profiling") },
      },
      build: {
        // Enable production source maps to easier debug deployed test studios
        sourcemap: true,
        rolldownOptions: {
          output: {
            // Disabling `mangle` (while keeping compression and whitespace removal) ensures that
            // the React DevTools components inspector has readable component names.
            // This overrides the `build.minify: 'oxc'` default set by `sanity build`, replacing
            // `esbuild: {minifyIdentifiers: false}` which the rolldown-powered Vite silently ignores.
            minify: { compress: true, mangle: false, codegen: true },
          },
        },
      },
    });

v3.4.2

Compare Source

Patch Changes

v3.4.1

Compare Source

Patch Changes

v3.4.0

Compare Source

Minor Changes
  • #​2410 e151988 Thanks @​stipsan! - update dependency @​sanity/icons to ^5.2.0

    @sanity/ui now imports every icon from its per-icon export path (e.g. @sanity/icons/Close) instead of the root barrel, so only the handful of icons the components actually render are pulled into your bundle.

Patch Changes

v3.3.6

Compare Source

Patch Changes
sanity-io/sanity (@​sanity/vision)

v6.6.0

Compare Source

Bug Fixes
sanity-io/sanity (sanity)

v6.6.0

Compare Source

Features
  • core: accept native table container definitions in the table plugin config (fdb9635)
  • core: add built-in table editing for Portable Text inputs (395437a)
  • presentation: share variant to presentation using comlink (#​13616) (88167dd)
  • releases: add option to update existing drafts when publishing a release (#​13400) (c7dd73c)
  • variants: add confirmation dialog for delete variant action (#​13546) (36916e6)
  • variants: enable editing variant documents through the document form (#​13505) (46d84dc)
  • variants: support document actions, diffs, comments and history for variant documents (#​13156) (9c1d7a2)
  • workbench entry (#​12511) (eef97ef)
Bug Fixes
Performance Improvements
  • core: deduplicate document version and permission subscriptions (#​13390) (7eba912)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 5am"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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

@renovate
renovate Bot requested a review from a team as a code owner July 17, 2026 15:11
@renovate
renovate Bot enabled auto-merge (squash) July 17, 2026 15:11
@renovate

renovate Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 24 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 11, reused 0, downloaded 0, added 0
Progress: resolved 23, reused 0, downloaded 0, added 0
Progress: resolved 27, reused 0, downloaded 0, added 0
Progress: resolved 30, reused 0, downloaded 0, added 0
Progress: resolved 44, reused 0, downloaded 0, added 0
Progress: resolved 199, reused 0, downloaded 0, added 0
Progress: resolved 342, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/sanity-io/cli/packages/@repo/package.config:
 ERR_PNPM_NO_MATURE_MATCHING_VERSION  Version 1.33.0 (released 2 days ago) of lightningcss does not meet the minimumReleaseAge constraint

This error happened while installing the dependencies of @sanity/pkg-utils@11.0.13

The latest release of lightningcss is "1.33.0". Published at 7/20/2026

If you need the full list of all 43 published versions run "pnpm view lightningcss versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude

@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch 9 times, most recently from c36c286 to 072ba9a Compare July 20, 2026 06:40
@renovate renovate Bot changed the title fix(deps): update dependency @sanity/pkg-utils to ^11.0.10 fix(deps): update dependency @sanity/pkg-utils to ^11.0.11 Jul 20, 2026
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 072ba9a to d8ea442 Compare July 20, 2026 08:16
@renovate renovate Bot changed the title fix(deps): update dependency @sanity/pkg-utils to ^11.0.11 fix(deps): update dependency @sanity/pkg-utils to ^11.0.13 Jul 20, 2026
Comment thread pnpm-workspace.yaml
'@swc/cli': ^0.8.1
rimraf: ^6.0.1
'@sanity/pkg-utils': ^11.0.9
'@sanity/pkg-utils': ^11.0.13

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Catalog/lockfile version mismatch

Medium Severity

The catalog bumps @sanity/pkg-utils to ^11.0.13, but pnpm-lock.yaml still records specifier ^11.0.9 and resolves 11.0.9. With pnpm install --frozen-lockfile in CI, installs fail on the catalog/lockfile mismatch, so the intended update never applies.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit d8ea442. Configure here.

@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from d8ea442 to ed4655b Compare July 20, 2026 08:51
@renovate renovate Bot changed the title fix(deps): update dependency @sanity/pkg-utils to ^11.0.13 fix(deps): update sanity-tooling Jul 20, 2026
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from b274b5f to d988733 Compare July 20, 2026 09:19
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from f9d263f to 034ef73 Compare July 20, 2026 10:13
Comment thread pnpm-workspace.yaml
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 7756735 to 32b751c Compare July 20, 2026 10:21

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 3 total unresolved issues (including 2 from previous reviews).

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 3542fb4. Configure here.

"@repo/package.config": "workspace:*",
"@repo/tsconfig": "workspace:*",
"@sanity/client": "^7.23.2",
"@sanity/client": "^7.24.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lockfile not updated with deps

High Severity

Manifests bump @sanity/client to ^7.24.0 and @sanity/pkg-utils to ^11.0.13, but pnpm-lock.yaml still pins 7.23.2 / 11.0.9 (including catalog and overrides). CI runs pnpm install --frozen-lockfile, so installs fail and the intended versions never resolve.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 3542fb4. Configure here.

@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 62502af to b793a4c Compare July 20, 2026 21:40
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 63357c4 to 19b6d60 Compare July 20, 2026 22:28
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from d9e2498 to 8edf579 Compare July 20, 2026 22:34
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from e8ce2d6 to 04999ae Compare July 20, 2026 22:49
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from f23b5e0 to 7363132 Compare July 21, 2026 09:22
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 38e296e to de1674c Compare July 21, 2026 15:12
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from a4069bc to 53f2c92 Compare July 21, 2026 19:07
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 8aba057 to e339e4f Compare July 21, 2026 20:24
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 274ec95 to 519ff35 Compare July 22, 2026 10:26
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 351c9f0 to bf6be0c Compare July 22, 2026 10:56
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from d3d2061 to ceeffee Compare July 22, 2026 11:04
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 728c1e9 to ef078e3 Compare July 22, 2026 16:44
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 96750f2 to 183f13f Compare July 22, 2026 21:23
@renovate
renovate Bot force-pushed the renovate/sanity-tooling branch from 5877a08 to 5efd4e0 Compare July 22, 2026 21:49
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