Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 20, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@sanity/pkg-utils (source) ^6.13.4^10.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)

v8.1.29

Compare Source

Bug Fixes

v8.1.28

Compare Source

Bug Fixes

v8.1.27

Compare Source

Bug Fixes

v8.1.26

Compare Source

Bug Fixes

v8.1.25

Compare Source

Bug Fixes

v8.1.24

Compare Source

Bug Fixes

v8.1.23

Compare Source

Bug Fixes

v8.1.22

Compare Source

Bug Fixes

v8.1.21

Compare Source

Bug Fixes

v8.1.20

Compare Source

Bug Fixes
  • add minimumReleaseAge 3 days policy (f71fa0c)

v8.1.19

Compare Source

Bug Fixes

v8.1.17

Compare Source

Bug Fixes
  • deps: Update dependency rolldown to v1.0.0-beta.40 (#​1998) ([5a632e

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

@socket-security
Copy link

socket-security bot commented Jan 20, 2026

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​prettier@​3.7.4 ⏵ 3.8.19010097 +196100
Updatednpm/​@​sanity/​pkg-utils@​6.13.4 ⏵ 10.4.497 +2100100100100

View full report

@socket-security
Copy link

socket-security bot commented Jan 20, 2026

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
License policy violation: npm typescript

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: ?npm/@sanity/pkg-utils@10.4.4npm/typescript@5.8.2

ℹ Read more on: This package | This alert | What is a license policy violation?

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 support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@5.8.2. 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/sanity-pkg-utils-10.x branch 4 times, most recently from bb197cd to 23cc9f4 Compare January 30, 2026 10:47
@renovate renovate bot force-pushed the renovate/sanity-pkg-utils-10.x branch 2 times, most recently from 05387a6 to 0625798 Compare February 3, 2026 12:01
@renovate renovate bot force-pushed the renovate/sanity-pkg-utils-10.x branch from 0625798 to 5d9ee6b Compare February 3, 2026 23:27
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