chore(deps): update all non-major dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@iconify-json/lucide	^1.2.118 → ^1.2.120
@nuxt/module-builder	^1.0.2 → ^1.0.3
@supabase/ssr	^0.12.1 → ^0.12.3
@supabase/supabase-js (source)	^2.110.4 → ^2.110.9
@types/node (source)	^26.1.1 → ^26.1.2
eslint (source)	^10.7.0 → ^10.8.0
pnpm (source)	11.13.0 → 11.17.0
pnpm (source)	11.15.0 → 11.17.0
typescript (source)	5.6.3 → 5.9.3
vite (source)	^8.1.4 → ^8.1.5
vue-tsc (source)	^3.3.7 → ^3.3.8

---

Release Notes

nuxt/module-builder (@​nuxt/module-builder)

v1.0.3

Compare Source

v1.0.3 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes

• update command defaults and descriptions (#​677)

📦 Build

• migrate to tsdown (#​765)

🏡 Chore

• migrate to pnpm v11 (#​738)
• remove shamefully-hoist (#​580)
• migrate resolutions/pnpm.overrides to pnpm-workspace.yaml (cfb45fb)
• migrate npm badges and links to npmx.dev (afcf2fa)
• revert pnpm trust policy and restore provenance action (aeb1d38)
• update pnpm to 10.21 and enable trust policy (92eb2af)

✅ Tests

• accept nuxt/app specifier for NuxtError in snapshot (809c89f)
• update v4.5 error type as well (9412c91)
• accept either #app or nuxt/app in generated declarations (#​727)

🤖 CI

• use uppt release workflow (604d5b3)
• add agent-scan workflow to flag bot-authored PRs (4442a14)
• rename workflow (f7be1a6)
• avoid checkout in reproduction (57e7ce9)
• pin github actions to full-length commit shas (c3c8e72)
• add provenance action to check for downgrades in provenance (d87d217)
• run tests on node 20 (54c5f13)

🎉 New Contributors

• Damian Głowala (@​DamianGlowala)

❤️ Contributors

• Daniel Roe (@​danielroe)
• Damian Głowala (@​DamianGlowala)
• Bobbie Goede (@​BobbieGoede)

supabase/ssr (@​supabase/ssr)

v0.12.3

Compare Source

Bug Fixes

• cookies: keep domain-scoped deletion in name-keyed cookie stores (#​258) (d3a8a98), closes #​256

v0.12.2

Compare Source

Bug Fixes

• align parseCookieHeader return type with getAll cookie method (#​239) (e8fe1d5), closes #​115

supabase/supabase-js (@​supabase/supabase-js)

v2.110.9

Compare Source

This was a version bump only for @​supabase/supabase-js to align it with other projects, there were no code changes.

v2.110.8

Compare Source

🩹 Fixes

• supabase: skip Node warning in Deno (#​2541)

❤️ Thank You

• Vaibhav @​7ttp

v2.110.7

Compare Source

🩹 Fixes

• realtime: trigger set auth on INITIAL_SESSION event (#​2531)

❤️ Thank You

• Filipe Cabaço @​filipecabaco

v2.110.6

Compare Source

2.110.6 (2026-07-15)

🩹 Fixes

• postgrest: type hinted self-referencing embeds as arrays (#​2520)
• realtime: forward opts to send() in track() (#​2490)
• supabase: warn instead of throw for unrecognized sb_ API key subtypes (#​2526)

❤️ Thank You

• Franco Kaddour @​FrancoKaddour
• Katerina Skroumpelou @​mandarini

v2.110.5

Compare Source

2.110.5 (2026-07-14)

🩹 Fixes

• supabase: avoid edge runtime warning (#​2522)

❤️ Thank You

• Vaibhav @​7ttp

eslint/eslint (eslint)

v10.8.0

Compare Source

Features

• 2fee9bb feat: export ConfigObject from eslint/config (#​21082) (sethamus)

Bug Fixes

• 6b8d2f7 fix: escape reserved characters in rule id in html formatter (#​21129) (Francesco Trotta)
• 9091071 fix: prevent no-unreachable-loop crash when all loop types are ignored (#​21116) (Pixel)
• e23fafe fix: prefer-object-spread add semicolon when adding parenthesis (#​21081) (synthex-byte)
• 20b5ad0 fix: quadratic-time regex in prefer-template (#​21096) (Milos Djermanovic)
• 8b6f6c0 fix: apply ignore configs to computed methods in class-methods-use-this (#​21094) (Pixel)
• b2c608c fix: NewExpression with parenthesized callee in preserve-caught-error (#​21083) (Francesco Trotta)

Documentation

• 6ddf858 docs: fix broken Specify Parser Options anchor link (#​21106) (Minsu)
• 784dfbe docs: Clarify no-eq-null description (#​21120) (Park Harin)
• 7ec733a docs: Fix typos and grammar in glossary (#​21095) (Marry (Subin Yang))
• 92bb13f docs: replace quake link (#​21108) (Jung Hyeon Jun)
• 68eb4a5 docs: fix broken Specify Globals anchor links in rule pages (#​21103) (Minsu)
• d28f697 docs: replace Code Climate CLI links with Qlty CLI links (#​21099) (Jung Hyeon Jun)
• eccc68d docs: correct --suppressions-location option description (#​21093) (Ga eun Lee)
• c5963f7 docs: Update README (GitHub Actions Bot)

Chores

• 4fbf46d test: pin webpack version to 5.108.4 (#​21137) (Francesco Trotta)
• 2d063e2 chore: update HTTP URLs to HTTPS in JSDoc and comments (#​21101) (Bo Hyun Kim)
• eccbe7b test: add error locations to no-class-assign (#​21123) (devoil)
• e7d1e43 ci: bump actions/setup-go from 6 to 7 (#​21118) (dependabot[bot])
• e9d66d0 ci: bump actions/setup-node from 6 to 7 (#​21119) (dependabot[bot])
• ee225b6 test: Add error location details to no-eq-null rule (#​21117) (Park Harin)
• 044a627 chore: update minimatch to ^10.2.5 (#​21107) (김채영)
• fb09aa8 chore: update ecosystem plugins (#​21115) (ESLint Bot)
• 5abd878 test: add error locations to no-proto (#​21114) (Gihyeon Jeong / 정기현)
• 9715887 test: Add error location details to no-div-regex (#​21110) (Park Harin)
• a746ec6 test: add error locations to no-new-wrappers (#​21109) (Gihyeon Jeong / 정기현)
• 8dde645 test: add error locations to no-ex-assign (#​21102) (devoil)
• 13ab0ec test: add error locations to no-label-var (#​21098) (Gihyeon Jeong / 정기현)
• a99906f test: Add error location details to no-delete-var rule (#​21105) (Park Harin)
• c47e8dc chore: add missing backticks to languages/js/index.js (#​21104) (beeen)
• 0174428 chore: add missing backticks to translate-cli-options.js (#​21097) (dongkyu lee)
• 3d36589 chore: add missing backticks to serialization.js (#​21091) (이규환)
• dcc9312 test: add error locations to eqeqeq (#​21090) (Ga eun Lee)
• 2710b18 ci: Add explicit permissions to rebuild-docs-sites workflow (#​21089) (Marry (Subin Yang))
• 5d2f866 chore: update dependency prettier to v3.9.5 (#​21086) (renovate[bot])
• d584e31 chore: fix failing ecosystem test for eslint-plugin-unicorn (#​21084) (Francesco Trotta)
• bf3eda0 chore: update ecosystem plugins (#​21079) (ESLint Bot)

pnpm/pnpm (pnpm)

v11.17.0: pnpm 11.17

Compare Source

Minor Changes

• Added a new setting, update.githubActionsServer, for specifying the base URL of the GitHub server that hosts the repositories of the GitHub Actions referenced by the workflow files (for example, a GitHub Enterprise Server). When the setting is not defined, the URL is read from the GITHUB_SERVER_URL environment variable, falling back to https://github.com. The URL must use the https:// or http:// protocol #​13220.

  pnpm outdated and pnpm update no longer fail when the refs of a GitHub Action's repository cannot be read (for example, when the action's repository is private or hosted on a different GitHub server). Such actions are now skipped with a warning.

  Setting update.githubActions to false now makes pnpm outdated and the interactive pnpm update skip GitHub Actions dependencies.

Patch Changes

• The token poll for web-based authentication no longer reads the body of non-OK or still-pending (HTTP 202) responses, and caps the token response body it does read at 64 KiB, so a malicious or compromised registry cannot exhaust memory through the poll pnpm/pnpm#12721.

• Fixed catalog: references in dependencies and overrides failing to resolve when installing through a pnpr server, which errored with "No catalog entry '' was found for catalog 'default'." even though the catalog entry existed. Also fixed a crash on Windows when installing a nested workspace member (e.g. packages/foo) through a pnpr server #​13232.

• Republished every package: the tarballs published by the v11.13.1 through v11.16.0 releases were missing most of their compiled files due to a packing bug #​13164.

• Revert script ordering change for pnpm run --sequential /regex/

• Support the from-git argument in the pnpm version command.

• When the authentication URL cannot be rendered as a QR code (for example when it exceeds the maximum QR data capacity), web-based login now displays the URL alone with a warning instead of aborting authentication pnpm/pnpm#12721.

Platinum Sponsors

Gold Sponsors

v11.16.0: pnpm 11.16

Compare Source

Minor Changes

• The first release of a package now publishes the version written in its manifest verbatim, instead of bumping off it. pnpm version -r and pnpm change status check the registry for each release's current version; when that version is not yet published, the package debuts at it and its pending changesets apply only from the next release. A newly added package seeded at 1100.0.0 with a minor changeset is therefore published as 1100.0.0 rather than skipping straight to 1100.1.0.

• Added a --changeset flag to pnpm update. Set update.changeset to true in pnpm-workspace.yaml to enable this behavior by default, and use --no-changeset to override the setting for one update. After the update completes, pnpm writes a .changeset/pnpm-update-<suffix>.md file declaring a patch bump for every workspace package whose dependencies or optionalDependencies were changed by the update and a major bump when peerDependencies changed, including packages that consume an updated catalog entry via the catalog: protocol. Private packages, packages without a name, and packages listed in the ignore array of .changeset/config.json are skipped. If .changeset/config.json does not exist, a warning is printed and no changeset is generated.

• Added GitHub Actions dependencies to pnpm outdated and interactive pnpm update. Non-interactive updates can include them with --include-github-actions or by setting update.githubActions to true in pnpm-workspace.yaml. Updated actions are pinned to exact commit hashes with their release tags preserved in comments.

• Added update and audit settings sections to pnpm-workspace.yaml, superseding the awkwardly named updateConfig, auditConfig, and top-level auditLevel settings:

  update:
    ignoreDeps: # was updateConfig.ignoreDependencies
      - webpack
      - "@​babel/*"
  
  audit:
    level: high # was auditLevel
    ignore: # was auditConfig.ignoreGhsas
      - GHSA-xxxx-yyyy-zzzz

  update.ignoreDeps lists dependency name patterns that pnpm update and pnpm outdated should skip. audit.level and audit.ignore tune pnpm audit.

  The deprecated updateConfig, auditConfig, and auditLevel settings keep working until the next major version. When both a new section value and its deprecated counterpart are set, the new section takes precedence and a warning is printed. Both the TypeScript CLI and the Rust config surface (pacquet) recognize the new sections.

Patch Changes

• Fixed pnpm add --save-exact/--save-prefix and pnpm update writing a package's version with the peerDependencies range's prefix (e.g. ^19.2.7 instead of the requested 19.2.7) whenever the same package also appeared in peerDependencies. A real dependencies/devDependencies/optionalDependencies entry now takes precedence over a same-named peerDependencies entry when computing the current specifiers #​13108.

Platinum Sponsors

Gold Sponsors

v11.15.1

Compare Source

v11.15.0: pnpm 11.15

Compare Source

Minor Changes

• Optional peer dependencies declared only via peerDependenciesMeta (for example debug's supports-color peer) are now resolved from a satisfying version already present in the dependency graph, the same way explicitly declared optional peer dependencies are. Previously such peers were only resolved this way when the package's metadata was read back from the lockfile, so an unrelated dependency change could rewrite peer resolutions across the whole lockfile.

Patch Changes

• Updated adm-zip to prevent crafted ZIP archives from causing excessive memory allocation.

• pnpm version -r no longer writes a versioning-ledger entry with no consumed intents as a bare intents: key, which the next run failed to read with ERR_PNPM_INVALID_VERSIONING_LEDGER. Empty intent lists are now written as intents: [], and the ledger reader accepts the bare form left by earlier releases.

• Fixed pnpr workspace resolution to preserve project names and versions for workspace: dependencies.

Platinum Sponsors

Gold Sponsors

v11.14.0: pnpm 11.14

Compare Source

Minor Changes

• peerDependencies now accept dependency specifiers that carry a scheme — a named-registry spec (<registry>:<version>), an npm: alias, or a file:/git/URL spec — instead of rejecting them with ERR_PNPM_INVALID_PEER_DEPENDENCY_SPECIFICATION #​13095. Such a peer is matched against the semver range carried by the specifier (work:5.x.x is checked as 5.x.x, npm:bar@^5 as ^5), or against * when it carries no version, while the original specifier still selects the package to auto-install. Bare name@version values, which are almost always a mistake, are still rejected.

• Added pnpm doctor, which diagnoses the pnpm installation and the environment it runs in: the versions and install method, whether the global bin directory is on PATH, whether the store and cache are writable, which link strategies (reflink, hardlink, symlink) the store's filesystem supports, registry connectivity, and an offline file: install that exercises the resolve/store/link path end to end. Each check reports how to fix what it finds, and the command exits non-zero when any check fails.

  Use --offline to skip the checks that need network access, --json for machine-readable output, and --benchmark to time the filesystem and install checks.

• Added support for executing multiple scripts matching a RegExp passed to pnpm run (e.g., pnpm run "/^build:.*/"), running matched scripts in deterministic lexicographical order. Restored the --sequential (-s) CLI option for pnpm run, which forces workspaceConcurrency to 1 so that matched scripts run sequentially one by one across and within packages.

Patch Changes

• Fixed pnpm install failing with ERR_PNPM_LOCKFILE_IS_SYMLINK when pnpm-lock.yaml is a symlink, as build sandboxes such as Bazel and Nix stage it #​13073. Reading a lockfile through a symlink is allowed again, and an install that leaves the lockfile unchanged no longer rewrites it, so --frozen-lockfile no longer needs to write at all. Writing a changed lockfile through a symlink is still refused, as that would redirect the write onto the symlink's target.

• Fixed frozen installs incorrectly treating equivalent Git dependency specifiers as a stale lockfile. See #​13039.

• pnpm owner ls now reports authentication and authorization failures (401/403) as dedicated errors that include the registry's response body, matching pnpm owner add/rm, instead of a generic Failed to fetch owners message.

• Recover from a metadata cache entry that disappears (concurrent cache cleanup, antivirus) after the registry has already answered the conditional request with 304 Not Modified. The metadata is re-requested once without cache validators instead of failing the install with ERR_PNPM_CACHE_MISSING_AFTER_304.

• A project pinned to a broken pnpm release via packageManager or devEngines.packageManager now reports which release is broken and what to do about it, instead of failing inside the installer. pnpm self-update already refused these releases; the version switch does too.

• Prevent broken-lockfile errors from including snippets of the lockfile's contents.

• pnpm self-update now checks that the version it installed can run before making it the active pnpm. A release that installs but cannot execute is discarded with an error instead of replacing a working installation.

• Fixed an out-of-memory regression when workspace projects concurrently resolve a package with large registry metadata pnpm/pnpm#13077.

• Fixed pnpm update rewriting exact version pins that use the = operator (for example =3.5.1) to a caret range (^3.5.1). Exact pins are now preserved and written back as the bare version. See #​12745.

Platinum Sponsors

Gold Sponsors

v11.13.1: pnpm 11.13.1

Compare Source

Patch Changes

• Fixed pnpm pack applying workspace-root ignore rules when a workspace package has its own .npmignore file.
• Keep the interactive minimumReleaseAge approval prompt visible during pnpm install. The progress reporter now pauses its redraws while a prompt is waiting for input instead of overwriting it, so the install no longer hangs on a question the user cannot see #​13019.
• Fixed pnpm self-update failing to link native platform binaries stored in sibling global virtual store slots.

microsoft/TypeScript (typescript)

v5.9.3: TypeScript 5.9.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC).
• No specific changes for TypeScript 5.9.2 (Stable)
• fixed issues query for Typescript 5.9.3 (Stable).

Downloads are available on:

• npm

v5.9.2: TypeScript 5.9

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC).
• No specific changes for TypeScript 5.9.2 (Stable)

Downloads are available on:

• npm

v5.8.3: TypeScript 5.8.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).
• fixed issues query for Typescript 5.8.1 (RC).
• fixed issues query for Typescript 5.8.2 (Stable).
• fixed issues query for Typescript 5.8.3 (Stable).

Downloads are available on:

• npm

v5.8.2: TypeScript 5.8

Compare Source

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).
• [fixed issues query for Typescript 5.8.1 (RC)]

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "on Monday"
• 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.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
supabase	Error		Jul 28, 2026 8:36pm
supabase-demo	Error		Jul 28, 2026 8:36pm

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxtjs/supabase@613

commit: db22820

[renovate]

⚠️ 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 3 workspace projects
? Verifying lockfile against supply-chain policies (1804 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 15, reused 0, downloaded 0, added 0
Progress: resolved 19, reused 0, downloaded 0, added 0
Progress: resolved 22, reused 0, downloaded 0, added 0
Progress: resolved 23, reused 0, downloaded 0, added 0
Progress: resolved 24, reused 0, downloaded 0, added 0
[WARN] Request took 12301ms: https://registry.npmjs.org/typescript
Progress: resolved 25, reused 0, downloaded 0, added 0
Progress: resolved 26, reused 0, downloaded 0, added 0
Progress: resolved 217, reused 0, downloaded 0, added 0
Progress: resolved 235, reused 0, downloaded 0, added 0
✓ Lockfile passes supply-chain policies (1804 entries in 17.7s)
Progress: resolved 237, reused 0, downloaded 0, added 0
Progress: resolved 239, reused 0, downloaded 0, added 0
Progress: resolved 348, reused 0, downloaded 2, added 0
Progress: resolved 412, reused 0, downloaded 2, added 0
Progress: resolved 447, reused 0, downloaded 2, added 0
Progress: resolved 528, reused 0, downloaded 2, added 0
Progress: resolved 705, reused 0, downloaded 2, added 0
Progress: resolved 712, reused 0, downloaded 2, added 0
Progress: resolved 714, reused 0, downloaded 2, added 0
Progress: resolved 715, reused 0, downloaded 2, added 0
Progress: resolved 718, reused 0, downloaded 2, added 0
Progress: resolved 724, reused 0, downloaded 2, added 0
Progress: resolved 829, reused 0, downloaded 4, added 0
Progress: resolved 941, reused 0, downloaded 4, added 0
Progress: resolved 1163, reused 0, downloaded 4, added 0
Progress: resolved 1168, reused 0, downloaded 4, added 0
Progress: resolved 1403, reused 0, downloaded 4, added 0
Progress: resolved 1545, reused 0, downloaded 4, added 0
Progress: resolved 1550, reused 0, downloaded 4, added 0
Progress: resolved 1631, reused 0, downloaded 4, added 0
Progress: resolved 1751, reused 0, downloaded 4, added 0
Progress: resolved 1787, reused 0, downloaded 4, added 0
Progress: resolved 1807, reused 0, downloaded 4, added 0
Progress: resolved 1809, reused 0, downloaded 4, added 0
[ERR_PNPM_NO_MATURE_MATCHING_VERSION] 8 versions do not meet the minimumReleaseAge constraint:
  @supabase/auth-js@2.110.9 was published at 2026-07-27T15:14:10.684Z, within the minimumReleaseAge cutoff (2026-07-26T20:35:34.440Z)
  @supabase/functions-js@2.110.9 was published at 2026-07-27T15:14:04.369Z, within the minimumReleaseAge cutoff (2026-07-26T20:35:34.440Z)
  @supabase/postgrest-js@2.110.9 was published at 2026-07-27T15:14:04.554Z, within the minimumReleaseAge cutoff (2026-07-26T20:35:34.440Z)
  @supabase/realtime-js@2.110.9 was published at 2026-07-27T15:14:04.976Z, within the minimumReleaseAge cutoff (2026-07-26T20:35:34.440Z)
  @supabase/storage-js@2.110.9 was published at 2026-07-27T15:14:10.098Z, within the minimumReleaseAge cutoff (2026-07-26T20:35:34.440Z)
  @supabase/supabase-js@2.110.9 was published at 2026-07-27T15:14:16.445Z, within the minimumReleaseAge cutoff (2026-07-26T20:35:34.440Z)
  @types/node@26.1.2 was published at 2026-07-27T17:32:14.992Z, within the minimumReleaseAge cutoff (2026-07-26T20:35:34.440Z)
  @types/node@26.1.2 was published at 2026-07-27T17:32:14.992Z, within the minimumReleaseAge cutoff (2026-07-26T20:35:34.440Z)