Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 14, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Confidence Type Update
@sanity/image-url (source) 1.1.0 -> 1.2.0 age confidence dependencies minor
@types/node (source) 20.19.7 -> 20.19.17 age confidence devDependencies patch
@types/react (source) 18.3.23 -> 18.3.24 age confidence devDependencies patch
@typescript-eslint/eslint-plugin (source) 8.36.0 -> 8.44.1 age confidence devDependencies minor
@typescript-eslint/parser (source) 8.36.0 -> 8.44.1 age confidence devDependencies minor
actions/checkout v4.2.2 -> v4.3.0 age confidence action minor
eslint-config-next (source) 14.2.30 -> 14.2.33 age confidence devDependencies patch
geist (source) 1.4.2 -> 1.5.1 age confidence dependencies minor
next-sanity (source) 9.12.2 -> 9.12.3 age confidence dependencies patch
pnpm (source) 10.13.1 -> 10.17.1 age confidence packageManager minor
react-hook-form (source) 7.60.0 -> 7.63.0 age confidence dependencies minor
react-social-icons (source) 6.24.0 -> 6.25.0 age confidence dependencies minor
typescript (source) 5.8.3 -> 5.9.2 age confidence devDependencies minor

Release Notes

sanity-io/image-url (@​sanity/image-url)

v1.2.0

Compare Source

Minor Changes
Patch Changes

All notable changes will be documented in this file.

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.44.1

Compare Source

🩹 Fixes
  • eslint-plugin: [await-thenable] should not report passing values to promise aggregators which may be a promise in an array literal (#​11611)
  • eslint-plugin: [no-unsafe-enum-comparison] support unions of literals (#​11599)
  • eslint-plugin: [no-base-to-string] make ignoredTypeNames match type names without generics (#​11597)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.44.0

Compare Source

🚀 Features
  • eslint-plugin: [await-thenable] report invalid (non-promise) values passed to promise aggregator methods (#​11267)
🩹 Fixes
  • eslint-plugin: [no-unnecessary-type-conversion] ignore enum members (#​11490)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.43.0

Compare Source

🚀 Features
  • typescript-estree: disallow empty type parameter/argument lists (#​11563)
🩹 Fixes
  • eslint-plugin: [prefer-return-this-type] don't report an error when returning a union type that includes a classType (#​11432)
  • eslint-plugin: [no-deprecated] should report deprecated exports and reexports (#​11359)
  • eslint-plugin: [no-floating-promises] allowForKnownSafeCalls now supports function names (#​11423, #​11430)
  • eslint-plugin: [consistent-type-exports] fix declaration shadowing (#​11457)
  • eslint-plugin: [no-unnecessary-type-conversion] only report ~~ on integer literal types (#​11517)
  • scope-manager: exclude Program from DefinitionBase node types (#​11469)
  • eslint-plugin: [no-non-null-assertion] do not suggest optional chain on LHS of assignment (#​11489)
  • type-utils: add union type support to TypeOrValueSpecifier (#​11526)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.42.0

Compare Source

🩹 Fixes
  • deps: update eslint monorepo to v9.33.0 (#​11482)

You can read about our versioning strategy and releases on our website.

v8.41.0

Compare Source

🩹 Fixes
  • deps: update dependency prettier to v3.6.2 (#​11496)

You can read about our versioning strategy and releases on our website.

v8.40.0

Compare Source

🚀 Features
  • typescript-estree: forbid invalid keys in EnumMember (#​11232)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.39.1

Compare Source

This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.39.0

Compare Source

🚀 Features
  • eslint-plugin: [only-throw-error] support yield/await expressions (#​11417)
  • eslint-plugin: add no-unnecessary-type-conversion to strict-type-checked ruleset (#​11427)
  • update to TypeScript 5.9.2 (#​11445)
  • eslint-plugin: [naming-convention] add enumMember PascalCase default option (#​11127)
🩹 Fixes
  • eslint-plugin: [no-unsafe-assignment] add an unsafeObjectPattern message (#​11403)
  • eslint-plugin: [prefer-optional-chain] ignore check option for most RHS of a chain (#​11272)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.38.0

Compare Source

🩹 Fixes
  • disallow extra properties in rule options (#​11397)
  • eslint-plugin: [consistent-generic-constructors] resolve conflict with isolatedDeclarations if enabled in constructor option (#​11351)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.37.0

Compare Source

🩹 Fixes
  • eslint-plugin: [unified-signatures] fix false positives for ignoreOverloadsWithDifferentJSDoc option (#​11381)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.44.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.44.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.43.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.42.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.41.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.40.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.39.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.39.0

Compare Source

🚀 Features
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.38.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.37.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

actions/checkout (actions/checkout)

v4.3.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/checkout@v4...v4.3.0

vercel/next.js (eslint-config-next)

v14.2.33

Compare Source

v14.2.32

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • fix router handling when setting a location response header #​82588
Credits

Huge thanks to @​ztanner for helping!

v14.2.31

Compare Source

vercel/geist-font (geist)

v1.5.1

Compare Source

sanity-io/next-sanity (next-sanity)

v9.12.3

Compare Source

Bug Fixes
pnpm/pnpm (pnpm)

v10.17.1

Compare Source

Patch Changes
  • When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #​9974.
  • Fix state.json creation path when executing pnpm patch in a workspace project #​9733.
  • When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #​9987.

v10.17.0

Compare Source

Minor Changes
  • The minimumReleaseAgeExclude setting now supports patterns. For instance:

    minimumReleaseAge: 1440
    minimumReleaseAgeExclude:
      - "@​eslint/*"

    Related PR: #​9984.

Patch Changes
  • Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #​9978.
  • When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #​9979.

v10.16.1

Compare Source

Patch Changes
  • The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result #​9963.
  • Forcibly disable ANSI color codes when generating patch diff #​9914.

v10.16.0

Compare Source

Minor Changes
  • There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

    The new setting is called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

    If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:

    minimumReleaseAgeExclude:
      - webpack

    Related issue: #​9921.

  • Added support for finders #​9946.

    In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:

    pnpm why minimist
    

    prints the chain of dependencies to any installed instance of minimist:

    verdaccio 5.20.1
    ├─┬ handlebars 4.7.7
    │ └── minimist 1.2.8
    └─┬ mv 2.1.1
      └─┬ mkdirp 0.5.6
        └── minimist 1.2.8
    

    What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have react@17 in their peer dependencies?

    This is now possible with "finder functions". Finder functions can be declared in .pnpmfile.cjs and invoked with the --find-by=<function name> flag when running pnpm list or pnpm why.

    Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our .pnpmfile.cjs:

    module.exports = {
      finders: {
        react17: (ctx) => {
          return ctx.readManifest().peerDependencies?.react === "^17.0.0";
        },
      },
    };

    Now we can use this finder function by running:

    pnpm why --find-by=react17
    

    pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.

    @&#8203;apollo/client 4.0.4
    ├── @&#8203;graphql-typed-document-node/core 3.2.0
    └── graphql-tag 2.12.6
    

    It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:

    module.exports = {
      finders: {
        react17: (ctx) => {
          const manifest = ctx.readManifest();
          if (manifest.peerDependencies?.react === "^17.0.0") {
            return `license: ${manifest.license}`;
          }
          return false;
        },
      },
    };

    Every matched package will also print out the license from its package.json:

    @&#8203;apollo/client 4.0.4
    ├── @&#8203;graphql-typed-document-node/core 3.2.0
    │   license: MIT
    └── graphql-tag 2.12.6
        license: MIT
    
Patch Changes
  • Fix deprecation warning printed when executing pnpm with Node.js 24 #​9529.
  • Throw an error if nodeVersion is not set to an exact semver version #​9934.
  • pnpm publish should be able to publish a .tar.gz file #​9927.
  • Canceling a running process with Ctrl-C should make pnpm run return a non-zero exit code #​9626.

v10.15.1

Compare Source

Patch Changes
  • Fix .pnp.cjs crash when importing subpath #​9904.
  • When resolving peer dependencies, pnpm looks whether the peer dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies #​9913.

v10.15.0

Compare Source

Minor Changes
  • Added the cleanupUnusedCatalogs configuration. When set to true, pnpm will remove unused catalog entries during installation #​9793.
  • Automatically load pnpmfiles from config dependencies that are named @*/pnpm-plugin-* #​9780.
  • pnpm config get now prints an INI string for an object value #​9797.
  • pnpm config get now accepts property paths (e.g. pnpm config get catalog.react, pnpm config get .catalog.react, pnpm config get 'packageExtensions["@&#8203;babel/parser"].peerDependencies["@&#8203;babel/types"]'), and pnpm config set now accepts dot-leading or subscripted keys (e.g. pnpm config set .ignoreScripts true).
  • pnpm config get --json now prints a JSON serialization of config value, and pnpm config set --json now parses the input value as JSON.
Patch Changes
  • Semi-breaking. When automatically installing missing peer dependencies, prefer versions that are already present in the direct dependencies of the root workspace package #​9835.
  • When executing the pnpm create command, must verify whether the node version is supported even if a cache already exists #​9775.
  • When making requests for the non-abbreviated packument, add */* to the Accept header to avoid getting a 406 error on AWS CodeArtifact #​9862.
  • The standalone exe version of pnpm works with glibc 2.26 again #​9734.
  • Fix a regression in which pnpm dlx pkg --help doesn't pass --help to pkg #​9823.

v10.14.0

Compare Source

Minor Changes
  • Added support for JavaScript runtime resolution

    Declare Node.js, Deno, or Bun in devEngines.runtime (inside package.json) and let pnpm download and pin it automatically.

    Usage example:

    {
      "devEngines": {
        "runtime": {
          "name": "node",
          "version": "^24.4.0",
          "onFail": "download" (we only support the "download" value for now)
        }
      }
    }

    How it works:

    1. pnpm install resolves your specified range to the latest matching runtime version.
    2. The exact version (and checksum) is saved in the lockfile.
    3. Scripts use the local runtime, ensuring consistency across environments.

    Why this is better:

    1. This new setting supports also Deno and Bun (vs. our Node-only settings useNodeVersion and executionEnv.nodeVersion)
    2. Supports version ranges (not just a fixed version).
    3. The resolved version is stored in the pnpm lockfile, along with an integrity checksum for future validation of the Node.js content's validity.
    4. It can be used on any workspace project (like executionEnv.nodeVersion). So, different projects in a workspace can use different runtimes.
    5. For now devEngines.runtime setting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.

    Related PR: #​9755.

  • Add --cpu, --libc, and --os to pnpm install, pnpm add, and pnpm dlx to customize supportedArchitectures via the CLI #​7510.

Patch Changes
  • Fix a bug in which pnpm add downloads packages whose libc differ from pnpm.supportedArchitectures.libc.
  • The integrities of the downloaded Node.js artifacts are verified #​9750.
  • Allow dlx to parse CLI flags and options between the dlx command and the command to run or between the dlx command and -- #​9719.
  • pnpm install --prod should removing hoisted dev dependencies #​9782.
  • Fix an edge case bug causing local tarballs to not re-link into the virtual store. This bug would happen when changing the contents of the tarball without renaming the file and running a filtered install.
  • Fix a bug causing pnpm install to incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.
react-hook-form/react-hook-form (react-hook-form)

v7.63.0: Version 7.63.0

Compare Source

🥢 feat: extract form values by form state (#​12936)

getValues(undefined, { dirtyFields: true }); // return only dirty fields 
getValues(undefined, { touchedFields: true });  // return only touched fields 

🦍 feat: improve get dirty fields logic (#​13049)
🐿️ chore: remove duplicated function isMessage (#​13050)
🐞 fix: use field name to update isValidating fields (#​13000)
🐞 fix: unregister previous field when switching conditional Controllers (#​13041)
🐞 fix: only excuse trigger function when deps has a valid array (#​13056)

thanks to @​candymask0712, @​GorkemKir, @​kimtaejin3, @​m2na7 & @​abnud11

v7.62.0

Compare Source

v7.61.1: Version 7.61.1

Compare Source

Revert "⌨️ fix: watch return type based on defaultValue (#​12896)"

v7.61.0

Compare Source

couetilc/react-social-icons (react-social-icons)

v6.25.0

Compare Source

v6.25.0

microsoft/TypeScript (typescript)

v5.9.2

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

👻 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 was generated by Mend Renovate. View the repository job log.

Copy link

vercel bot commented Jul 14, 2025

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

Project Deployment Preview Comments Updated (UTC)
portfolio Ready Ready Preview Comment Sep 25, 2025 6:55pm

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a9f5c3e to d1e5276 Compare July 15, 2025 07:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d1e5276 to d00bdf7 Compare July 19, 2025 03:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d00bdf7 to 98a0e2e Compare July 22, 2025 00:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 98a0e2e to 63666e2 Compare July 24, 2025 02:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 63666e2 to 117f0a2 Compare July 24, 2025 12:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 117f0a2 to 17f5047 Compare July 30, 2025 23:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 17f5047 to 024759e Compare July 31, 2025 17:44
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 024759e to 4ea1092 Compare August 1, 2025 01:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4ea1092 to 6efc431 Compare August 2, 2025 01:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6efc431 to 083c2c2 Compare August 4, 2025 17:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 083c2c2 to 0258bfd Compare August 8, 2025 17:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0258bfd to c58f668 Compare August 10, 2025 14:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c58f668 to 726e9aa Compare August 11, 2025 14:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 726e9aa to 58b742d Compare August 11, 2025 17:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2b4695a to 87021e4 Compare September 4, 2025 12:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 87021e4 to 63f405b Compare September 4, 2025 16:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 63f405b to 1b0250e Compare September 8, 2025 18:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1b0250e to 006326d Compare September 9, 2025 21:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 006326d to 9ecb862 Compare September 13, 2025 00:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9ecb862 to e4473c1 Compare September 13, 2025 23:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e4473c1 to ff4a905 Compare September 15, 2025 22:44
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ff4a905 to 7612aa5 Compare September 17, 2025 01:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7612aa5 to 2fe5d38 Compare September 17, 2025 18:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2fe5d38 to 2fb540b Compare September 18, 2025 03:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2fb540b to d14625d Compare September 20, 2025 01:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d14625d to 031fabd Compare September 22, 2025 17:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 031fabd to ba071b0 Compare September 24, 2025 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants