chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@iconify-json/lucide	^1.2.44 -> ^1.2.47
@iconify-json/simple-icons	^1.2.35 -> ^1.2.38
@types/node (source)	^22.15.21 -> ^22.15.31
drizzle-orm (source)	^0.43.1 -> ^0.44.2
eslint (source)	^9.27.0 -> ^9.28.0
pnpm (source)	10.11.0 -> 10.12.1
workers-ai-provider	^0.5.2 -> ^0.6.0
wrangler (source)	^4.16.1 -> ^4.19.1

---

Release Notes

drizzle-team/drizzle-orm (drizzle-orm)

v0.44.2

Compare Source

• [BUG]: Fixed type issues with joins with certain variations of tsconfig: #​4535, #​4457

v0.44.1

Compare Source

• [BUG]: Drizzle can no longer run on Durable Objects

v0.44.0

Compare Source

Error handling

Starting from this version, we’ve introduced a new DrizzleQueryError that wraps all errors from database drivers and provides a set of useful information:

1. A proper stack trace to identify which exact Drizzle query failed
2. The generated SQL string and its parameters
3. The original stack trace from the driver that caused the DrizzleQueryError

Drizzle cache module

Drizzle sends every query straight to your database by default. There are no hidden actions, no automatic caching or invalidation - you’ll always see exactly what runs. If you want caching, you must opt in.

By default, Drizzle uses a explicit caching strategy (i.e. global: false), so nothing is ever cached unless you ask. This prevents surprises or hidden performance traps in your application. Alternatively, you can flip on all caching (global: true) so that every select will look in cache first.

Out first native integration was built together with Upstash team and let you natively use upstash as a cache for your drizzle queries

import { upstashCache } from "drizzle-orm/cache/upstash";
import { drizzle } from "drizzle-orm/...";

const db = drizzle(process.env.DB_URL!, {
  cache: upstashCache({
    // 👇 Redis credentials (optional — can also be pulled from env vars)
    url: '<UPSTASH_URL>',
    token: '<UPSTASH_TOKEN>',
    // 👇 Enable caching for all queries by default (optional)
    global: true,
    // 👇 Default cache behavior (optional)
    config: { ex: 60 }
  })
});

You can also implement your own cache, as Drizzle exposes all the necessary APIs, such as get, put, mutate, etc.
You can find full implementation details on the website

import Keyv from "keyv";
export class TestGlobalCache extends Cache {
  private globalTtl: number = 1000;
  // This object will be used to store which query keys were used
  // for a specific table, so we can later use it for invalidation.
  private usedTablesPerKey: Record<string, string[]> = {};
  constructor(private kv: Keyv = new Keyv()) {
    super();
  }
  // For the strategy, we have two options:
  // - 'explicit': The cache is used only when .$withCache() is added to a query.
  // - 'all': All queries are cached globally.
  // The default behavior is 'explicit'.
  override strategy(): "explicit" | "all" {
    return "all";
  }
  // This function accepts query and parameters that cached into key param,
  // allowing you to retrieve response values for this query from the cache.
  override async get(key: string): Promise<any[] | undefined> {
    ...
  }
  // This function accepts several options to define how cached data will be stored:
  // - 'key': A hashed query and parameters.
  // - 'response': An array of values returned by Drizzle from the database.
  // - 'tables': An array of tables involved in the select queries. This information is needed for cache invalidation.
  //
  // For example, if a query uses the "users" and "posts" tables, you can store this information. Later, when the app executes
  // any mutation statements on these tables, you can remove the corresponding key from the cache.
  // If you're okay with eventual consistency for your queries, you can skip this option.
  override async put(
    key: string,
    response: any,
    tables: string[],
    config?: CacheConfig,
  ): Promise<void> {
    ...
  }
  // This function is called when insert, update, or delete statements are executed.
  // You can either skip this step or invalidate queries that used the affected tables.
  //
  // The function receives an object with two keys:
  // - 'tags': Used for queries labeled with a specific tag, allowing you to invalidate by that tag.
  // - 'tables': The actual tables affected by the insert, update, or delete statements,
  //   helping you track which tables have changed since the last cache update.
  override async onMutate(params: {
    tags: string | string[];
    tables: string | string[] | Table<any> | Table<any>[];
  }): Promise<void> {
    ...
  }
}

For more usage example you can check our docs

eslint/eslint (eslint)

v9.28.0

Compare Source

pnpm/pnpm (pnpm)

v10.12.1

Minor Changes

• Experimental. Added support for global virtual stores. When enabled, node_modules contains only symlinks to a central virtual store, rather to node_modules/.pnpm. By default, this central store is located at <store-path>/links (you can find the store path by running pnpm store path).

  In the central virtual store, each package is hard linked into a directory whose name is the hash of its dependency graph. This allows multiple projects on the system to symlink shared dependencies from this central location, significantly improving installation speed when a warm cache is available.

  This is conceptually similar to how NixOS manages packages, using dependency graph hashes to create isolated and reusable package directories.

  To enable the global virtual store, set enableGlobalVirtualStore: true in your root pnpm-workspace.yaml, or globally via:

  pnpm config -g set enable-global-virtual-store true

  NOTE: In CI environments, where caches are typically cold, this setting may slow down installation. pnpm automatically disables the global virtual store when running in CI.

  Related PR: #​8190

• The pnpm update command now supports updating catalog: protocol dependencies and writes new specifiers to pnpm-workspace.yaml.
• Added two new CLI options (--save-catalog and --save-catalog-name=<name>) to pnpm add to save new dependencies as catalog entries. catalog: or catalog:<name> will be added to package.json and the package specifier will be added to the catalogs or catalog[<name>] object in pnpm-workspace.yaml #​9425.
• Semi-breaking. The keys used for side-effects caches have changed. If you have a side-effects cache generated by a previous version of pnpm, the new version will not use it and will create a new cache instead #​9605.
• Added a new setting called ci for explicitly telling pnpm if the current environment is a CI or not.

Patch Changes

• Sort versions printed by pnpm patch using semantic versioning rules.
• Improve the way the error message displays mismatched specifiers. Show differences instead of 2 whole objects #​9598.
• Revert #​9574 to fix a regression #​9596.

v10.11.1

Compare Source

Patch Changes

• Fix an issue in which pnpm deploy --legacy creates unexpected directories when the root package.json has a workspace package as a peer dependency #​9550.
• Dependencies specified via a URL that redirects will only be locked to the target if it is immutable, fixing a regression when installing from GitHub releases. (#​9531)
• Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #​9505.
• Use pnpm_config_ env variables instead of npm_config_ #​9571.
• Fix a regression (in v10.9.0) causing the --lockfile-only flag on pnpm update to produce a different pnpm-lock.yaml than an update without the flag.
• Let pnpm deploy work in repos with overrides when inject-workspace-packages=true #​9283.
• Fixed the problem of path loss caused by parsing URL address. Fixes a regression shipped in pnpm v10.11 via #​9502.
• pnpm -r --silent run should not print out section #​9563.

cloudflare/ai (workers-ai-provider)

v0.6.0

Compare Source

Minor Changes

• #​181 9f5562a Thanks @​JoaquinGimenez1! - Adds support for new tool call format during streaming

v0.5.3

Compare Source

Patch Changes

• de992e6 Thanks @​threepointone! - trigger a release for reverted change

cloudflare/workers-sdk (wrangler)

v4.19.1

Compare Source

Patch Changes

• #​9456 db2cdc6 Thanks @​WillTaylorDev! - Fix bug causing preview alias to always be generated.

v4.19.0

Compare Source

Minor Changes

• #​9401 03b8c1c Thanks @​WillTaylorDev! - Provide ability for Wrangler to upload preview aliases during version upload.

Patch Changes

• #​9390 80e75f4 Thanks @​penalosa! - Support additional Mixed Mode resources in Wrangler:

  • AI
  • Browser
  • Images
  • Vectorize
  • Dispatch Namespaces

• #​9395 b3be057 Thanks @​Maximo-Guk! - Add WRANGLER_CI_OVERRIDE_NETWORK_MODE_HOST for Workers CI

• #​9410 87f3843 Thanks @​dario-piotrowicz! - enable consumers of unstable_readConfig to silence remote warnings

• Updated dependencies [8c7ce77, 80e75f4, 80e75f4, fac2f9d, 92719a5]:

  • [email protected]

v4.18.0

Compare Source

Minor Changes

• #​9393 34b6174 Thanks @​jamesopstad! - Hard fail on Node.js < 20. Wrangler no longer supports Node.js 18.x as it reached end-of-life on 2025-04-30. See https://github.com/nodejs/release?tab=readme-ov-file#end-of-life-releases.

Patch Changes

• #​9308 d3a6eb3 Thanks @​dario-piotrowicz! - expose new utilities and types to aid consumers of the programmatic mixed-mode API

  Specifically the exports have been added:

  • Experimental_MixedModeSession: type representing a mixed-mode session
  • Experimental_ConfigBindingsOptions: type representing config-bindings
  • experimental_pickRemoteBindings: utility for picking only the remote bindings from a record of start-worker bindings.
  • unstable_convertConfigBindingsToStartWorkerBindings: utility for converting config-bindings into start-worker bindings (that can be passed to startMixedModeSession)

• #​9347 b8f058c Thanks @​penalosa! - Improve binding display on narrower terminals

• Updated dependencies [d9d937a, e39a45f, fdae3f7]:

  • [email protected]

v4.17.0

Compare Source

Minor Changes

• #​9321 6c03bde Thanks @​petebacondarwin! - Add support for FedRAMP High compliance region

  Now it is possible to target Wrangler at the FedRAMP High compliance region.
  There are two ways to signal to Wrangler to run in this mode:

  • set "compliance_region": "fedramp_high" in a Wrangler configuration
  • set CLOUDFLARE_COMPLIANCE_REGION=fedramp_high environment variable when running Wrangler

  If both are provided and the values do not match then Wrangler will exit with an error.

  When in this mode OAuth authentication is not supported.
  It is necessary to authenticate using a Cloudflare API Token acquired from the Cloudflare FedRAMP High dashboard.

  Most bindings and commands are supported in this mode.

  • Unsupported commands may result in API requests that are not supported - possibly 422 Unprocessable Entity responses.
  • Unsupported bindings may work in local dev, as there is no local validation, but will fail at Worker deployment time.

  Resolves DEVX-1921.

• #​9330 34c71ce Thanks @​edmundhung! - Updated internal configuration to use Miniflare’s new defaultPersistRoot instead of per-plugin persist flags

• #​8973 cc7fae4 Thanks @​Caio-Nogueira! - Show latest instance by default on workflows instances describe command

Patch Changes

• #​9335 6479fc5 Thanks @​penalosa! - Redesign wrangler dev to more clearly present information and have a bit of a glow up ✨
  

• #​9329 410d985 Thanks @​penalosa! - Hide logs in the startMixedModeSession() API

• #​9325 c2678d1 Thanks @​edmundhung! - refactor: fallbacks to local image binding from miniflare when local mode is enabled

• Updated dependencies [34c71ce, f7c82a4, 7ddd865, 6479fc5, e5ae13a]:

  • [email protected]

---

Configuration

📅 Schedule: Branch creation - "on Monday" (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.

👻 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.

[nuxthub-admin]

✅ Deployed chat-template

Deployed chat-template 33309c8 to preview

🔗	renovate-all-minor-patch.chat-template.pages.dev
📌	28dfe074.chat-template.pages.dev
📱	View QR Code

📋 View deployment logs