chore(deps): update all non-major dependencies by renovate[bot] · Pull Request #256 · unjs/db0

renovate · 2026-09-03T02:30:36Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@cloudflare/workers-types	`^5.20260901.1` → `^5.20260929.1`
@libsql/client (source)	`^0.17.4` → `^0.18.0`
@planetscale/database	`^1.20.1` → `^1.20.2`
@types/bun (source)	`^1.4.0` → `^1.4.2`
db0	`^0.3.4` → `^0.4.1`
drizzle-orm (source)	`1.0.0-rc.4` → `1.0.0-rc.5-ab785fc`
eslint (source)	`^10.9.1` → `^10.11.0`
kysely (source)	`^0.29.5` → `^0.29.6`
mysql2 (source)	`^3.24.2` → `^3.24.5`
obuild	`^0.4.38` → `^0.4.40`
pnpm (source)	`11.22.0` → `11.28.2`
prettier (source)	`^3.9.6` → `^3.9.9`
undocs	`0.10.1-20260818-142856-3b64b18` → `0.10.1-20260922-215730-10f5034`
wrangler (source)	`^4.127.1` → `^4.143.1`

⚠️ Renovate does not enforce Minimum Release Age for bump, lockfileUpdate, or rollback updates, so these are raised without a Minimum Release Age check. You will need to manually validate the Minimum Release Age for these package(s).

Release Notes

cloudflare/workerd (@cloudflare/workers-types)

tursodatabase/libsql-client-ts (@libsql/client)

`v0.18.0`

Compare Source

planetscale/database-js (@planetscale/database)

`v1.20.2`

Compare Source

What's Changed

security: pin GitHub Actions to commit SHAs by @mattrobenolt in #200
security: harden GitHub Actions workflows by @mattrobenolt in #201
ci: add GitHub Actions security checks by @mattrobenolt in #202
Add a secure NPM configuration by @joshmgross in #203
Add CODEOWNERS by @joshmgross in #204
Resolve oustanding npm audit warnings by @joshmgross in #205
Update undici by @joshmgross in #206
Remove dependency on jest by @joshmgross in #207
Bump js-yaml from 4.1.1 to 4.3.1 by @dependabot[bot] in #215
Sanitization: Harden placeholder parsing by @no-itsbackpack in #218

New Contributors

@joshmgross made their first contribution in #203
@no-itsbackpack made their first contribution in #218

Full Changelog: planetscale/database-js@v1.20.1...v1.20.2

unjs/db0 (db0)

`v0.4.1`

Compare Source

compare changes

🚀 Enhancements

Add import specifier to connector dependencies (f3e2e93)

🏡 Chore

Update deps (a98d4e8)

❤️ Contributors

Pooya Parsa (@pi0)

`v0.4.0`

Compare Source

compare changes

🚀 Enhancements

drizzle: Support schema parameter (#183)
drizzle: Update with postgres and mysql connectors (#219)
Expose connector name (#205)
⚠️ Require explicit library passing to connectors (cc5f0fb)
Add neon for serverless postgres (#191)
Add database capabilities (#207)
Add prisma adapter (#210)
Add tracing channels support (#193)
drizzle: ⚠️ Upgrade to drizzle-orm v1 (#250)

🩹 Fixes

postgresql: Only rewrite ? placeholders outside string literals and comments (#248)
drizzle: Remap object rows to TS field names for all dialects (#227)

📖 Documentation

Add notice about sqlite3 not being maintained (#220)
Add connector docs for prisma postgres (#199)

📦 Build

Bundle dist entries (3b13154)

🏡 Chore

docs: Update lockfile (f70a51c)
Update deps (f45bdc4)
Update ci (da02ab1)
Update ci (f52a303)
Lint (b36b593)
Update deps (8277d72)
Use port-mapping in docker compose (#208)
Update deps (af13d78)
Apply automated updates (ebd8028)
Rename lint script (c180379)
Fix build script on windows (#204)
Add agents.md (8356a77)
Update deps (57babed)
Fix cf types (d2a0e70)
Disable eslint temporarily (8f3abb5)
Update undocs (079b75e)
Update deps (2d88f1c)
Update lock (2734147)

⚠️ Breaking Changes

⚠️ Require explicit library passing to connectors (cc5f0fb)
drizzle: ⚠️ Upgrade to drizzle-orm v1 (#250)

❤️ Contributors

Pooya Parsa (@pi0)
Pi0x x@pi0.io
Abdelrahman Awad (@logaretm)
Inesh Bose dev@inesh.xyz
Max (@onmax)
João Meyer (@meyer1994)
Atila Fassina atila.fassina@databricks.com
Mochammad Fadhlan Al-Ghiffari (@MFA-G)
Ankur Datta (@ankur-arch)
Adam Haglund (@beeequeue)

eslint/eslint (eslint)

`v10.11.0`

Compare Source

`v10.10.0`

Compare Source

kysely-org/kysely (kysely)

`v0.29.6`: 0.29.6

Compare Source

Hey 👋

A small batch of bug fixes. Please report any issues. 🤞😰🤞

🚀 Features

🐞 Bugfixes

PostgreSQL 🐘 / SQLite 📘

fix: allow immutable columns in doUpdateSet's where. by @igalklebanov in #2043

📖 Documentation

feat(site): grow the proof wall from npm's dependents (Cypress, Canton, Tailor, Supabase Lite) + verify every pin by @igalklebanov in #1985
Update link to Migrator API docs by @ardouglass in #1991

📦 CICD & Tooling

chore: bumps dependencies. by @igalklebanov in #2045

⚠️ Breaking Changes

🐤 New Contributors

@ardouglass made their first contribution in #1991

What's Changed

Full Changelog: kysely-org/kysely@v0.29.5...v0.29.6

sidorares/node-mysql2 (mysql2)

`v3.24.5`

Compare Source

Bug Fixes

strip the brackets from an IPv6 host in a connection URI (#4570) (b1c39c8)

`v3.24.4`

Compare Source

Performance Improvements

per-query overhead, local dates, short strings, TLS context and compression (#4522) (2387daf)
reuse TLS sessions across connections to the same server (#4529) (9178c82)

`v3.24.3`

Compare Source

Bug Fixes

typings: PoolCluster node events emit a string nodeId (#4513) (1281e1e)

pnpm/pnpm (pnpm)

`v11.28.2`: pnpm 11.28.2

Compare Source

pnpm 11.28.2 fixes pnpm install skipping every workspace project whose common ancestor is the filesystem root, and stops pnpm run from reinstalling or installing when nothing needs it.

Patch Changes

pnpm install reported success without installing anything when the workspace projects' common ancestor was the filesystem root, such as / or a drive root like C:\. It now installs these projects #16328.
verifyDepsBeforeRun no longer reports dependencies as outdated after a filtered install just because pnpm-lock.yaml has a newer modification time. It checks the lockfile against the packages that install put in place. Before, pnpm run reinstalled the whole workspace with lifecycle scripts on, for example after a Docker COPY brought in a lockfile with a newer mtime #16322.

After a filtered install, verifyDepsBeforeRun now also checks that the install put the selected projects' dependencies in place. A node_modules directory alone no longer counts as proof.
pnpm run and pnpm exec no longer install a project that has never been installed and has nothing to install. Such a project declares no dependencies, no peer dependencies that autoInstallPeers would fetch, and no install lifecycle scripts. The command now runs without writing node_modules or pnpm-lock.yaml #16313.

Platinum Sponsors

Gold Sponsors

`v11.28.1`: pnpm 11.28.1

Compare Source

pnpm 11.28.1 makes pnpm install work in StackBlitz WebContainers, repairs lockfiles whose patch hashes disagree with patchedDependencies, and fixes many bugs in Windows command shims, injected workspace dependencies, and pnpm deploy.

Patch Changes

Installing packages

pnpm install now works in StackBlitz WebContainers. On projects without a lockfile, it used to fail with ENOENT ... pnpm-lock.yaml, because pnpm did not recognize the errors that WebContainers return from asynchronous file system calls. It also failed with "this.db.exec is not a function", because node:sqlite there lacks DatabaseSync.exec. When node:sqlite cannot prepare statements either, pnpm stores the index in index.fallback #15649.
pnpm install now completes after downloading a Node.js runtime specified by devEngines.runtime when pnpm runs on Node.js 24.4.x #14667.
pnpm install no longer fails when a package from the registry declares a file: dependency on a directory inside itself, such as "@types/css-tree": "file:./typings/css-tree". pnpm links that dependency to the directory inside the package, as npm and Yarn do. The lockfile records it as link:<root>/typings/css-tree #9141.
Installing a git-hosted dependency that has to be built no longer fails when that dependency's own dependencies have build scripts nobody approved. pnpm skips those builds while preparing the dependency, as it does without strictDepBuilds #9764.
pnpm now uses pnpm to prepare a git-hosted dependency that is a pnpm workspace without a committed lockfile. It used npm before, which could skip the dependency's build #14011.
When installing a git dependency over SSH fails with Permission denied (publickey), pnpm suggests checking the loaded keys with ssh-add -l. Resolving an SSH URL that refuses the key also shows a local HTTPS rewrite that leaves the recorded URL alone #13743.
pnpm install --dev and pnpm fetch --dev now install the optional dependencies of devDependencies, such as the platform binaries of Biome and oxlint. The project's own optionalDependencies are still skipped #9678.
pnpm install --frozen-lockfile now works on a detached HEAD when gitBranchLockfile is enabled. The install now reads the lockfiles of the local and remote-tracking branches that contain the checked-out commit. It still writes the shared pnpm-lock.yaml #7672.
pnpm install on CI now fails on an outdated lockfile when preferFrozenLockfile is explicitly set to true. Setting it to true used to let CI update the lockfile #9072.
pnpm install now fails with ERR_PNPM_IGNORED_BUILDS on a repeat install when strictDepBuilds is on and a dependency's build is still undecided. A repeat install against an existing node_modules reported success where a fresh install failed #10450.
pnpm install now removes an optional dependency from node_modules if its install script fails. Code that checks whether the package is installed no longer finds a package that cannot load #8756.
pnpm install --offline and pnpm add --offline now resolve a version range to the newest matching version whose tarball is already in the store. They used to pick the newest version in the cached metadata and fail with ERR_PNPM_NO_OFFLINE_TARBALL when its tarball was missing #10715.
If an offline install fails because the registry metadata cache uses the layout from before pnpm 11.27 and 12.4, the error now names the older mirror on disk and explains that one online install repopulates the cache #15656.
pnpm install now fails right away when writing package files fails because the store is full. It no longer retries the tarball download first #8581.
With nodeLinker: hoisted, pnpm install now restores a workspace project's node_modules after it was deleted. Before, the install printed "Already up to date" and left the project without the dependencies nested under it.
Under nodeLinker: hoisted, pnpm install now clears orphaned package directories that an interrupted or failed install leaves in a project's node_modules. A directory recorded by the previous install is removed, while an unrecorded directory is moved to node_modules/.ignored. A copy already in .ignored is never overwritten #13676.
Packages in an external virtualStoreDir can resolve the project's direct dependencies selected by hoistPattern. Run pnpm install --force to repair an existing installation #5652.
A repeat install now keeps the fast path when a declared local file dependency is replaced by an override #12892.

Store, build cache, and global virtual store

Files imported from the store now follow the umask of the install that writes them. Installing with a umask of 077 no longer leaves imported files readable by the group and others #3807.
With the global virtual store, pnpm rebuild no longer modifies packages shared with projects that have not approved their build scripts #12302.
The side-effects cache now restores the symlinks that a build script creates inside a package. A warm install used to replace each of them with a copy of its target #12859.

After upgrading, every package with a build script is built once more.
pnpm install now restores cached build artifacts when reinstalling a workspace that uses separate lockfiles #12942.
The global virtual store and the side-effects cache now key built packages by the Node.js version that the root project's devEngines.runtime or engines.runtime pins. That is the Node.js their build scripts run with. A dependency that declares its own engines.runtime no longer changes the key for every other package.
Concurrent installs that share a global virtual store now run a package's build in its shared slot one at a time. A failed build leaves the slot in place and marks it for the next install to rebuild #15568.
Concurrent installs no longer fail when they replace the same stale hoisted dependency link. Virtual store cleanup now keeps the temporary lockfiles that concurrent installs are still writing.
pnpm install keeps the owner, group, and mode of files already in a shared store, including index.db. New store files and directories inherit the store directory's group-write bit. When that directory is setgid, new files inherit its group. pnpm does not change a file's owner or group #12765.
When pnpm install repairs a store file that was modified through a hard link in node_modules, the repair now keeps the file's inode on Linux and macOS. Hard-linked copies in other projects are healed at the same time. Before, only the project running the install received the restored content. On Windows the repair still replaces the file, so other projects are healed on their next install #3445.
A tarball whose integrity pnpm computed during download is now found in the store on the next install. Before, that install downloaded the tarball again once the lockfile recorded the integrity #12562.
pnpm now warns when it cannot hard link packages from an existing store in the pnpm home directory and uses a store on the project's filesystem. This can happen when the project is on another filesystem, such as a bind-mounted workspace in a container. The warning names both stores and suggests setting storeDir #14505.

Resolving and linking dependencies

A peer dependency no longer resolves to two different versions for one package. This happened when the package peer-depends on another package and on one of that package's peers, and it is installed deeper than a direct dependency of the package that provides them #12098.
An optional peer dependency is no longer resolved from another workspace project's package when the project provides one of that package's own peers at a version it rejects. This avoids bogus unmet peer errors #13989.
pnpm no longer reports unmet peer dependency warnings for aliased npm: peer ranges that a tarball dependency satisfies #11126.
pnpm install now links the executables of auto-installed peer dependencies into the workspace root's node_modules/.bin, including after a frozen-lockfile reinstall #8511.
With resolutionMode: time-based and minimumReleaseAge both set, pnpm install no longer reports a subdependency as too new when only the time-based cutoff excludes it. Such subdependencies used to fail a strict install with ERR_PNPM_NO_MATURE_MATCHING_VERSION, or were added to minimumReleaseAgeExclude #13569.

A transitive dependency that has no matching version published before the time-based cutoff now resolves to the lowest matching version allowed by minimumReleaseAge. pnpm picks a version younger than minimumReleaseAge only if no older version matches #16298.
With minimumReleaseAge set, re-resolving the lockfile no longer rewrites the peerDependencies recorded for a package whose version did not change. This happened when the registry metadata of a package differed from the package.json in its tarball #13988.
pnpm no longer revalidates cached registry metadata when the registry sends Cache-Control: max-age=0, no-cache, or no-store. It downloads the metadata again, so a version newly published to such a registry is visible on the next install #13487.
pnpm's built-in package compatibility database no longer applies to a project's own manifest. A project named like a published package, such as vue-loader, no longer gains dependencies on pnpm install or pnpm update. User-configured packageExtensions still apply to project manifests #11700.
Relative local tarball paths in pnpm.overrides without an explicit file: prefix are now rebased correctly for workspace packages #11131.
pnpm no longer reports pnpm-lock.yaml as broken when a project depends on a package named constructor. A __proto__ key in the lockfile is now kept as a plain entry when pnpm reads or writes the lockfile. It no longer replaces the prototype of the objects pnpm builds from it #11028.
With nodeLinker: pnp, a workspace package can now require another workspace package it depends on #3567. On Windows, workspace dependency paths in the generated .pnp.cjs now use forward slashes.

Performance

pnpm now uses less memory when installing a package whose archive is larger than 64 MiB unpacked, and when installing a runtime from a zip archive, such as Node.js on Windows, Deno, or Bun #14164.
A fresh install reusing a warm global virtual store skips reimporting packages whose target directory is already complete #11112.
A warm pnpm install reuses on-disk package metadata for five minutes when the registry does not send an ETag. Registries that send an ETag, including the public npm registry, still revalidate with a conditional request. pnpm update still fetches current metadata #13976.

Patched dependencies

pnpm install now repairs a pnpm-lock.yaml whose (patch_hash=<hash>) dependency paths disagree with its patchedDependencies map, including paths that lack the hash their patch calls for. pnpm previously accepted such a lockfile as up to date and kept the old patched files. pnpm install --frozen-lockfile now fails on such a lockfile with ERR_PNPM_INCONSISTENT_PATCH_HASH. It fails with ERR_PNPM_UNCHECKABLE_PATCH_HASH when a patch hash in the lockfile is malformed, or when the lockfile lacks the package version or patch entry that the check needs #15336.
pnpm install now fails with ERR_PNPM_PATCH_NOT_FOUND when a patch file listed in patchedDependencies does not exist. It used to fail with a raw ENOENT error and a stack trace #5268.
pnpm now fails with ERR_PNPM_INVALID_PATCHED_DEPENDENCY when patchedDependencies has an invalid shape or contains a non-string value.
engineStrict now checks the patched package.json when a patchedDependencies entry changes engines. A patch that relaxes engines.node no longer fails the install against the published range #9603.
pnpm patch now applies the existing patch file to the edit directory of a git-hosted dependency, as it already does for packages from the registry #9699.
pnpm patch-commit now fails with an error when git cannot be found in PATH. It previously reported that no changes were found #8666.

Workspaces and filtering

pnpm install refreshes injected copies of workspace packages when source projects are rebuilt. Injected copies previously stayed stale until pnpm install --force #4407.
Scripts listed in syncInjectedDepsAfterScripts now update injected dependencies while they run. A watcher on the injected package, such as a dev server, sees each change before the script exits #4410.
pnpm install no longer fails for an injected workspace dependency whose package publishes from a publishConfig.directory that its own prepare script builds. The injected copy now picks up that directory once prepare finishes building it. pnpm install --frozen-lockfile no longer reports the dependency as outdated while the directory has not been built yet #7811.
With sharedWorkspaceLockfile: false, an injected workspace package that has lifecycle scripts is now hard linked into the projects that depend on it. Before, pnpm left a plain copy, so later edits to the package did not reach those projects #9828.
injectWorkspacePackages now hard links a workspace dependency declared with a relative path, such as workspace:../foo, the same way it already does for workspace:* #10446.
pnpm install no longer creates a node_modules symlink inside the publishConfig.directory of a workspace package linked with linkDirectory. A build tool that cleaned its output directory through that symlink deleted the files of the package's dependencies. pnpm install also removes a symlink that an earlier install left there #16226.
When verifyDepsBeforeRun triggers an install before a filtered pnpm run or pnpm exec, pnpm now installs only the selected projects and their dependencies. A later filtered command also installs a selected project that an earlier filtered install skipped #11865.
pnpm import in a workspace now keeps the versions pinned by a yarn.lock inside a workspace project #4385.
Installing with pnprServer set now records the pnpmfile checksum in the lockfile, so a later pnpm install --frozen-lockfile accepts that lockfile. A frozen install through the pnpr server now fails if the pnpmfile changed. If the pnpmfile defines a readPackage, afterAllResolved or preResolution hook or custom resolvers, pnpm resolves dependencies locally and prints a warning that the pnpr server was not used #14460.

Installing through a pnpr server now links a workspace project at the directory its publishConfig.directory names. An install that resolves through a server which does not forward the setting fails with ERR_PNPM_PNPR_PUBLISH_DIRECTORY_MISMATCH. The server rejects a publishConfig.directory that points outside its project.

Adding, updating, and removing dependencies

With autoInstallPeers, pnpm add and pnpm remove in a workspace project keep the locked version of a peer dependency the project declares. In a workspace where another project depended on a different version of that package, the peer could switch to that version #11225.
Adding a dependency now keeps unrelated transitive dependencies on their locked versions #11456.
pnpm update --recursive <pkg> no longer changes the version of a peer dependency that another workspace project installs automatically. Such a peer could move to a version outside the range the project declares, for example to React 19 in a project that declares react: ^18.3.1 #14928.
pnpm update package@beta on a dependency declared as catalog: now updates the catalog entry and keeps catalog: in package.json. Before, pnpm wrote the resolved specifier to package.json #13399.
pnpm update now applies an override that references a catalog with the catalog's new value when the update bumps that catalog entry. Before, the packages the override targets kept the old version in the lockfile #12159.
pnpm add <dir> now warns when the added directory declares peer dependencies, as pnpm link does. The directory is saved as a link: dependency, and its peers are not resolved from the project that adds it. Use the file: protocol to have them resolved #5523.

Running scripts and commands

pnpm run and pnpm exec no longer install dependencies automatically when the root package.json still keeps overrides, packageExtensions, patchedDependencies, or ignoredOptionalDependencies in its pnpm field. pnpm no longer reads that field, so the install rewrote the lockfile without those settings. The command now fails and asks to move the settings to pnpm-workspace.yaml #16278.
pnpm run no longer reinstalls dependencies when a node_modules directory installed outside CI is used with CI=true, or the other way around #12337.
pnpm no longer hangs after a lifecycle script exits while a process it started in the background keeps the script's output open. pnpm stops reading that output one second after the script exits #5730.
A signal sent to pnpm, such as SIGTERM, now reaches the pnpm that pnpm switches to because of packageManager or devEngines.packageManager, and the one that pnpm with runs. The signal used to be dropped, so scripts running under that pnpm never got to shut down #9948.
pnpm run exits with the code of a script that handles Ctrl+C and shuts down. A script that finished cleanly is not reported as a lifecycle failure. The commands after it in the same script still run #9945.
pnpm run and lifecycle scripts use the configured scriptShell, including Git Bash on Windows, when shellEmulator is also enabled. shellEmulator still runs scripts when scriptShell is not set. Extra arguments passed to pnpm run are quoted for the shell that runs the script, so a Windows path stays intact #14719.
pnpm -r run /regexp/ now honors the tasks dependsOn declared for each script the selector matches, like running the script by name does. Matched scripts that depend on each other run in order. Each matched script runs once #15596.
Commands run from a POSIX shell through a dependency's own node_modules/.bin, such as node_modules/vite/node_modules/.bin/esbuild, no longer fail with MODULE_NOT_FOUND #10189.
pnpm rebuild with nodeLinker: hoisted no longer puts one package's parent node_modules/.bin directories on the PATH of the packages it builds after it.

Publishing, packing, and deploying

pnpm publish now waits at least 5 minutes for the registry to answer a publish request, like npm. This fixes "409 Conflict - Failed to save packument" errors when the registry is slow to answer #11454.
pnpm deploy with a shared lockfile now copies workspace dependencies into the deploy directory, even when packageImportMethod is set to hardlink. Previously, their files were hard-linked to the workspace s

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- "after 1am and before 5am"
Automerge
- "after 2am and before 5am"

🚦 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 · 2026-09-03T02:30:40Z

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

Project	Deployment	Actions	Updated
db0	Ready	Preview	Oct 2, 2026 8:26pm UTC

vercel Bot deployed to Preview September 3, 2026 02:31 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from cee10de to b960b76 Compare September 3, 2026 08:45

vercel Bot deployed to Preview September 3, 2026 08:45 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from b960b76 to 8459458 Compare September 3, 2026 23:46

vercel Bot deployed to Preview September 3, 2026 23:47 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 8459458 to c1352ab Compare September 4, 2026 19:46

vercel Bot deployed to Preview September 4, 2026 19:47 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from c1352ab to 8e298f1 Compare September 5, 2026 03:08

vercel Bot deployed to Preview September 5, 2026 03:09 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 8e298f1 to 7239fa5 Compare September 5, 2026 11:11

vercel Bot deployed to Preview September 5, 2026 11:12 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 7239fa5 to c0566ac Compare September 6, 2026 02:52

vercel Bot deployed to Preview September 6, 2026 02:53 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from c0566ac to 621c6c3 Compare September 6, 2026 18:49

vercel Bot deployed to Preview September 6, 2026 18:49 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 621c6c3 to 9e8f7ef Compare September 6, 2026 22:50

vercel Bot deployed to Preview September 6, 2026 22:51 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 9e8f7ef to 66036e9 Compare September 7, 2026 03:54

vercel Bot deployed to Preview September 7, 2026 03:54 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 66036e9 to 2b2a7f0 Compare September 7, 2026 20:00

vercel Bot deployed to Preview September 7, 2026 20:00 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 2b2a7f0 to d518f20 Compare September 8, 2026 02:42

vercel Bot deployed to Preview September 8, 2026 02:42 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from d518f20 to 58b20c9 Compare September 8, 2026 09:56

vercel Bot deployed to Preview September 8, 2026 09:56 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 58b20c9 to 690bd9b Compare September 9, 2026 03:49

vercel Bot deployed to Preview September 9, 2026 03:50 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 690bd9b to 56ad397 Compare September 9, 2026 14:12

vercel Bot deployed to Preview September 9, 2026 14:13 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 548fa42 to d1ccca8 Compare September 13, 2026 02:54

vercel Bot deployed to Preview September 13, 2026 02:55 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from d1ccca8 to f407fd3 Compare September 13, 2026 19:02

vercel Bot deployed to Preview September 13, 2026 19:02 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from f407fd3 to 1af3067 Compare September 14, 2026 03:21

vercel Bot deployed to Preview September 14, 2026 03:21 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 1af3067 to 249dc4b Compare September 14, 2026 20:55

vercel Bot deployed to Preview September 14, 2026 20:56 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 249dc4b to 2fb02ee Compare September 15, 2026 10:11

vercel Bot deployed to Preview September 15, 2026 10:12 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 2fb02ee to 71585a0 Compare September 15, 2026 22:40

vercel Bot deployed to Preview September 15, 2026 22:41 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 71585a0 to fb452e8 Compare September 16, 2026 03:16

vercel Bot deployed to Preview September 16, 2026 03:16 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from fb452e8 to f9a39be Compare September 16, 2026 17:42

vercel Bot deployed to Preview September 16, 2026 17:43 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from f9a39be to 4d5ece9 Compare September 17, 2026 04:43

vercel Bot deployed to Preview September 17, 2026 04:43 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 4d5ece9 to fda2f18 Compare September 17, 2026 22:02

vercel Bot deployed to Preview September 17, 2026 22:02 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from fda2f18 to da076d6 Compare September 18, 2026 03:28

vercel Bot deployed to Preview September 18, 2026 03:28 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from da076d6 to ac8d31d Compare September 18, 2026 23:04

vercel Bot deployed to Preview September 18, 2026 23:05 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from ac8d31d to b49d7b0 Compare September 19, 2026 03:45

vercel Bot deployed to Preview September 19, 2026 03:45 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from b49d7b0 to 83fc0ce Compare September 19, 2026 13:54

vercel Bot deployed to Preview September 19, 2026 13:54 View deployment

renovate Bot force-pushed the renovate/all-minor-patch branch from 83fc0ce to a86fdd3 Compare September 19, 2026 23:10

chore(deps): update all non-major dependencies

8ccd61c

Navigation Menu

chore(deps): update all non-major dependencies - #256

chore(deps): update all non-major dependencies#256
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

renovate Bot commented Sep 3, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Sep 3, 2026 •

edited

Loading

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

What's Changed

New Contributors

🚀 Enhancements

🏡 Chore

❤️ Contributors

🚀 Enhancements

🩹 Fixes

📖 Documentation

📦 Build

🏡 Chore

⚠️ Breaking Changes

❤️ Contributors

v0.29.6: 0.29.6

🚀 Features

🐞 Bugfixes

PostgreSQL 🐘 / SQLite 📘

📖 Documentation

📦 CICD & Tooling

⚠️ Breaking Changes

🐤 New Contributors

What's Changed

Bug Fixes

Performance Improvements

Bug Fixes

v11.28.2: pnpm 11.28.2

Patch Changes

Platinum Sponsors

Gold Sponsors

v11.28.1: pnpm 11.28.1

Patch Changes

Installing packages

Store, build cache, and global virtual store

Resolving and linking dependencies

Performance

Patched dependencies

Workspaces and filtering

Adding, updating, and removing dependencies

Running scripts and commands

Publishing, packing, and deploying

Configuration

Uh oh!

vercel Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Sep 3, 2026 •

edited

Loading

`v0.29.6`: 0.29.6

`v11.28.2`: pnpm 11.28.2

`v11.28.1`: pnpm 11.28.1

vercel Bot commented Sep 3, 2026 •

edited

Loading