Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 26, 2026

This PR contains the following updates:

Package Change Age Confidence
@sanity/pkg-utils (source) 8.1.2910.4.4 age confidence

Release Notes

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

v10.4.4

Compare Source

Patch Changes

v10.4.3

Compare Source

Patch Changes

v10.4.2

Compare Source

Patch Changes

v10.4.1

Compare Source

Patch Changes

v10.4.0

Compare Source

Minor Changes
  • #​2538 a7bd216 Thanks @​copilot-swe-agent! - Auto-enable styled-components compiler when detected as peer dependency. If styled-components is in peerDependencies and babel-plugin-styled-components is in devDependencies, the babel plugin is automatically enabled without requiring explicit configuration. Users can disable this behavior by setting babel: { styledComponents: false } in package.config.ts.
Patch Changes

v10.3.5

Compare Source

Patch Changes

v10.3.4

Compare Source

Patch Changes

v10.3.3

Compare Source

Patch Changes

v10.3.2

Compare Source

Patch Changes

v10.3.1

Compare Source

Patch Changes

v10.3.0

Compare Source

Minor Changes
Patch Changes

v10.2.6

Compare Source

Patch Changes

v10.2.5

Compare Source

Patch Changes

v10.2.4

Compare Source

Patch Changes

v10.2.3

Compare Source

Patch Changes

v10.2.2

Compare Source

Patch Changes

v10.2.1

Compare Source

Patch Changes

v10.2.0

Compare Source

Minor Changes
Patch Changes

v10.1.3

Compare Source

Patch Changes

v10.1.2

Compare Source

Patch Changes

v10.1.1

Patch Changes

v10.1.0

Minor Changes
Patch Changes

v10.0.0

Major Changes
  • #​2329 c5b81e7 Thanks @​stipsan! - The tsconfig presets have moved to a new package, pnpm install --save-dev @​sanity/tsconfig and update your imports in tsconfig.json files:

    • @sanity/pkg-utils/tsconfig/recommended.json -> @sanity/tsconfig/recommended
      {
      -  "extends": "@​sanity/pkg-utils/tsconfig/recommended.json"
      +  "extends": "@​sanity/tsconfig/recommended"
      }
    • @sanity/pkg-utils/tsconfig/strict.json -> @sanity/tsconfig/strict
      {
      -  "extends": "@​sanity/pkg-utils/tsconfig/strict.json"
      +  "extends": "@​sanity/tsconfig/strict"
      }
    • @sanity/pkg-utils/tsconfig/strictest.json -> @sanity/tsconfig/strictest
      {
      -  "extends": "@​sanity/pkg-utils/tsconfig/strictest.json"
      +  "extends": "@​sanity/tsconfig/strictest"
      }
    • @sanity/pkg-utils/tsconfig/isolated-declarations.json -> @sanity/tsconfig/isolated-declarations
      {
      -  "extends": ["@​sanity/pkg-utils/tsconfig/strictest.json", "@​sanity/pkg-utils/tsconfig/isolated-declarations.json"]
      +  "extends": ["@​sanity/tsconfig/strictest", "@​sanity/tsconfig/isolated-declarations"]
      }
  • #​2332 c99d52f Thanks @​stipsan! - Removed internal exports:

    import {
      build,
      check,
      createLogger,
      getExtractMessagesConfig,
      init,
      loadPkg,
      loadPkgWithReporting,
      parseExports,
      parseStrictOptions,
      watch,
    } from '@​sanity/pkg-utils'
  • #​2331 ae7b51c Thanks @​stipsan! - Removed noPackageJsonMain and noPackageJsonModule rules

v9.2.3

Compare Source

Patch Changes

v9.2.2

Compare Source

Patch Changes

v9.2.1

Compare Source

Patch Changes

v9.2.0

Compare Source

Minor Changes

v9.1.5

Compare Source

Patch Changes

v9.1.4

Compare Source

Patch Changes

v9.1.3

Compare Source

Patch Changes

v9.1.2

Compare Source

Patch Changes

v9.1.1

Compare Source

Patch Changes

v9.1.0

Compare Source

Minor Changes
  • #​2202 207f489 Thanks @​copilot-swe-agent! - feat: Add configurable strict checks for legacy package.json fields

    Added new strict options to warn about deprecated package.json fields that are no longer needed with modern Node.js and bundlers:

    • noPackageJsonMain - Warns when main field is present (use exports instead)
    • noPackageJsonModule - Warns when module field is present (use exports instead)
    • noPackageJsonBrowser - Warns when browser field is present (use browser condition in exports)
    • noPackageJsonTypesVersions - Warns when typesVersions field is present (TypeScript supports types condition in exports)
    • preferModuleType - Warns when type field is missing or set to commonjs (future versions will require "type": "module")

    All new checks default to warn level and are configurable via strictOptions in package.config.ts.

    BREAKING CHANGES:

    • Removed alwaysPackageJsonMain strict option (conflicted with the new noPackageJsonMain option)
    • The top-level types field is still required for npm package listings to show TypeScript support
  • #​2221 107c8a6 Thanks @​stipsan! - Update @microsoft/api-extractor to ^7.55.0 and @microsoft/tsdoc-config to ^0.18.0

Patch Changes

v9.0.9

Compare Source

Patch Changes

v9.0.8

Compare Source

Patch Changes

v9.0.6

Compare Source

Patch Changes

v9.0.5

Compare Source

Patch Changes

v9.0.4

Compare Source

Bug Fixes

v9.0.3

Compare Source

Bug Fixes

v9.0.2

Compare Source

Bug Fixes

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

⚠ BREAKING CHANGES
  • resolve package.config.ts as ESM when supported. This means that if the package.json has "type": "commonjs" then the package.config.ts can no longer use import/export keywords. If you're unable to start using "type": "module" you'll either have to rename to package.config.mts, or use require/module.exports instead.
Bug Fixes
Code Refactoring
  • resolve package.config.ts as ESM when supported. This means that if the package.json has "type": "commonjs" then the package.config.ts can no longer use import/export keywords. If you're unable to start using "type": "module" you'll either have to rename to package.config.mts, or use require/module.exports instead. (2c65e63)

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 Sanity. View repository job log here

@vercel
Copy link

vercel bot commented Jan 26, 2026

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

Project Deployment Actions Updated (UTC)
preview-kit-next-app-router Error Error Feb 3, 2026 11:10pm
preview-kit-next-pages-router Error Error Feb 3, 2026 11:10pm
preview-kit-remix Error Error Feb 3, 2026 11:10pm
preview-kit-test-studio Error Error Feb 3, 2026 11:10pm

Request Review

@socket-security
Copy link

socket-security bot commented Jan 26, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​@​types/​react@​19.2.9 ⏵ 19.2.10100 +110079 +194100
Updatednpm/​prettier@​3.6.2 ⏵ 3.8.190 -310097 +196100
Updatednpm/​isbot@​5.1.33 ⏵ 5.1.34100 +110010092 +1100
Updatednpm/​@​sanity/​pkg-utils@​8.1.29 ⏵ 10.4.497 +2100100100100

View full report

@renovate renovate bot force-pushed the renovate/sanity-pkg-utils-10.x branch from 33b1d3c to c1a8ccc Compare January 28, 2026 12:54
@renovate renovate bot force-pushed the renovate/sanity-pkg-utils-10.x branch from c1a8ccc to 374ce21 Compare January 28, 2026 19:47
@renovate renovate bot force-pushed the renovate/sanity-pkg-utils-10.x branch from 374ce21 to aeb152e Compare January 29, 2026 13:06
@renovate renovate bot force-pushed the renovate/sanity-pkg-utils-10.x branch from aeb152e to 6a0eced Compare January 30, 2026 11:15
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