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

renovate · 2026-07-15T03:36:08Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@cloudflare/workers-types	`^5` → `^5.20260809.1`
@types/pg (source)	`^8.20.0` → `^8.21.0`
eslint (source)	`^10.7.0` → `^10.8.1`
kysely (source)	`^0.29.3` → `^0.29.4`
mysql2 (source)	`^3.22.6` → `^3.23.2`
pg (source)	`^8.22.0` → `^8.23.0`
pnpm (source)	`11.12.0` → `11.20.0`
pnpm (source)	`10.19.0` → `10.34.5`
prettier (source)	`^3.9.5` → `^3.9.6`
undocs	`^0.4.10` → `^0.4.17`
wrangler (source)	`^4.110.0` → `^4.120.0`

⚠️ 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)

eslint/eslint (eslint)

`v10.8.1`

Compare Source

Bug Fixes

18eb0a7 fix: prevent ASI hazard in no-unused-labels autofix (#21173) (dongkyu lee)
151ba3f fix: false positives in getter-return and accessor-pairs (#21163) (Grit)
6898df9 fix: ignore meta-property names in id-denylist (#21166) (Pixel)
4d7db66 fix: ignore meta-property names in id-match (#21167) (Pixel)
677214e fix: handle ASI hazards in no-unused-vars removeVar suggestion (#20935) (kuldeep kumar)

Documentation

7d0cbf8 docs: Update README (GitHub Actions Bot)
0a05812 docs: add missing backticks to no-duplicate-imports.js (#21183) (Lee Daeun)
678c90b docs: Update README (GitHub Actions Bot)
8a10424 docs: Update README (GitHub Actions Bot)
69bb948 docs: Update README (GitHub Actions Bot)

Chores

0a14800 chore: update github/codeql-action action to v4.37.4 (#21196) (renovate[bot])
05adcb1 test: fix failing ecosystem test for eslint-plugin-unicorn (#21191) (Lazizbek Ergashev)
5611035 test: add error locations info to no-void (#21185) (Lee Daeun)
ee47333 ci: bump github/codeql-action from 4 to 4.37.3 (#21176) (dependabot[bot])
f131c03 chore: improve ecosystem test failure reporting (#20937) (crimsonjay0)
1f6edde chore: update ecosystem plugins (#21182) (ESLint Bot)
d3266fb chore: unpin webpack dependency (#21172) (Francesco Trotta)
65a6519 chore: add allowScripts field to package.json (#21092) (GiHoon Noh)
22e5256 ci: add triage:no label to Dependabot PRs (#21141) (lumir)
55c9038 ci: bump actions/labeler from 6 to 7 (#21159) (dependabot[bot])
7280e78 chore: update dependency prettier to v3.9.6 (#21162) (renovate[bot])
eddbad6 test: fix failing ecosystem test for eslint-plugin-unicorn (#21156) (Francesco Trotta)
60a178d chore: update ecosystem plugins (#21150) (ESLint Bot)
f9f61dc test: add error locations to no-unreachable (#21151) (JIYEON)
d086293 test: add error locations to no-undef (#21147) (JIYEON)
cc01b67 test: add error locations to no-useless-catch (#21144) (devoil)
688e75e chore: add missing backticks in JSDoc (#21143) (Bo Hyun Kim)
7c1e175 test: add error locations to require-await (#21145) (Grit)
588a26d test: add error locations to no-extra-label (#21139) (dongkyu lee)
059aa89 test: add error locations to no-useless-concat (#21140) (dongkyu lee)
5a452a8 test: add error locations to no-const-assign (#21138) (dongkyu lee)

`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)

kysely-org/kysely (kysely)

`v0.29.4`: 0.29.4

Compare Source

Hey 👋

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

🚀 Features

🐞 Bugfixes

PostgreSQL 🐘

fix: fix postgres password not being passed to control client by @CakeWithDivinity & @igalklebanov in #1944

SQLite 📘

fix(sqlite): returning clauses wrongfuly output after order by and limit in delete queries. by @igalklebanov in #1946

📖 Documentation

📦 CICD & Tooling

chore: bump dependencies. by @igalklebanov in #1945

⚠️ Breaking Changes

🐤 New Contributors

@CakeWithDivinity made their first contribution in #1944

What's Changed

Full Changelog: kysely-org/kysely@v0.29.3...v0.29.4

sidorares/node-mysql2 (mysql2)

`v3.23.2`

Compare Source

Bug Fixes

correct connectAttributes typo in ChangeUser packet (#4423) (f64ce07), closes #2140
don't leave a failed execute as the active command (#4425) (fbd64b6)

`v3.23.1`

Compare Source

Bug Fixes

security: fix unbounded decompression of server-supplied compressed packets, reported by alanturing881 (7c48343)
parser: call typeCast for NULL values in the binary protocol (#4394) (01f1092)

`v3.23.0`

Compare Source

Features

return unsafe integers inside JSON columns as exact strings with supportBigNumbers (#4388) (a26ff14)
sql-escaper: add Temporal support when escaping values (#4392) (6b933f6)
support MariaDB data types (UUID, INET4, INET6, VECTOR, JSON) via extended type metadata; run CI against MariaDB (#4373) (5034e57)

brianc/node-postgres (pg)

`v8.23.0`

Compare Source

Add support for query pipelineing.

pnpm/pnpm (pnpm)

`v11.20.0`: pnpm 11.20

Compare Source

Minor Changes

Security fix. Affects projects using namedRegistries on pnpm 11.1.0–11.19.x. It is semi-breaking for those projects — see "If you use named registries" below.

The lockfile recorded no marker for which registry a package came from. Packages were keyed by name@version alone, and entry lookup went through refToRelative(ref, name), so a dependency you declared against one registry could be satisfied by an entry that was actually resolved from another. When two registries served the same name and version, both collapsed onto a single packages: entry and whichever resolved first decided the tarball every consumer got.

That is a package-substitution risk: a package you expect from your private registry could be installed from a different registry that publishes the same name and version, and the lockfile recorded nothing that would let you tell.

Packages resolved from a named registry are now recorded under registry-qualified keys (<name>@<registryName>:<version>, e.g. foo@work:1.0.0), so each registry gets its own entry and the lockfile pins which one a dependency came from.

The lockfile format version is unchanged. Registry-qualified keys appear only for packages resolved from a named registry, so a project that does not use namedRegistries sees no difference, and older pnpm versions keep reading the file.

If you use named registries

Your next non-frozen install re-keys those entries, which shows up as a lockfile diff. Commit it — that diff is the fix being applied. Review it: an entry that moves to a registry you did not expect is worth investigating.

Everyone working on the project should be on this version or newer before you do. An older pnpm reads the re-keyed lockfile fine — frozen installs are unaffected — but it does not produce registry-qualified keys itself, so any install that updates the lockfile writes those entries back to the old shape, and the next install on a current pnpm re-qualifies them. The result is a lockfile that flips back and forth, and while it is in the old shape the project is exposed again. Because the lockfile format version is deliberately unchanged, pnpm cannot detect this and warn you about it.

There is no setting to keep the old behavior: the old shape is the vulnerability.

Tarball URLs that follow the standard registry layout are no longer written to the lockfile for named-registry packages; they are recomputed from the namedRegistries setting on demand.

To use named registries, map your aliases in pnpm-workspace.yaml:

namedRegistries:
  work: https://npm.enterprise.example.com/

New built-in `npmjs:` alias

npmjs: now resolves to https://registry.npmjs.org/ with no configuration, alongside the existing gh: alias for GitHub Packages. It pins a dependency to the public registry even when registry points elsewhere, such as an internal proxy:

{ "dependencies": { "left-pad": "npmjs:^1.3.0" } }

npm: cannot do this — it is the alias protocol (npm:<name>@<range>) and resolves through whatever registry points at.

If you mirror or proxy npmjs, point the alias at your mirror:

namedRegistries:
  npmjs: https://npm.internal.example.com/

Built-in registry URLs are also the prefixes a lockfile's recorded tarball URL is matched against when pnpm verifies a package. Without the override, an entry whose tarball URL is on registry.npmjs.org is verified against the public registry rather than your mirror. This only affects lockfiles that record such URLs — a canonical URL for your configured registry is omitted from the lockfile and unaffected — and only when a tarball-URL, minimumReleaseAge, or trustPolicy check runs. Overriding the alias is the same escape hatch GHES users already have for gh.

Every alias the lockfile references must stay in namedRegistries: reading an entry whose alias is gone fails with ERR_PNPM_MISSING_NAMED_REGISTRY rather than silently falling back to the default registry, since that would fetch a different package. Renaming an alias re-resolves the packages that used it.

Named registry aliases that shadow a reserved dependency specifier prefix (file, link, workspace, runtime, npm, jsr, ...) are now rejected with ERR_PNPM_RESERVED_NAMED_REGISTRY_NAME instead of being silently shadowed by the corresponding resolver.

pnpm licenses and pnpm sbom now keep the two artifacts apart as well: license records carry the registry alias, and SBOM components carry the purl repository_url qualifier.

Patch Changes

An empty http-proxy, https-proxy, proxy, or no-proxy value — from the .npmrc, pnpm-workspace.yaml, the CLI, or the HTTP_PROXY / HTTPS_PROXY / PROXY / NO_PROXY environment variables — no longer fails the install with ERR_PNPM_INVALID_PROXY. Empty settings read as unset, so a shell exporting HTTP_PROXY= disables the proxy, and an empty proxy= in the .npmrc no longer suppresses HTTPS_PROXY #13533.

proxy=false in the .npmrc or proxy: false in pnpm-workspace.yaml now turns proxying off instead of being read as a proxy host named false. false and null on https-proxy / http-proxy / no-proxy read as unset, and on the command line they are ordinary host names, since a flag carries its value verbatim.
The env lockfile no longer pins @pnpm/exe alongside pnpm when the wanted pnpm version is 12 or newer. From v12 the unscoped pnpm package is itself the native executable, so @pnpm/exe is not published for it and resolving it would fail. The engine identity check now verifies the native binary through whichever package ships it.
lexCompare and nerfDart are now published as @pnpm/text.ordinal-comparator and @pnpm/config.registry-auth-key. Use these instead of @pnpm/util.lex-comparator and @pnpm/config.nerf-dart.
Fixed the order in which pnpm matches a lockfile's recorded tarball URL against known registry URLs. Two registry URLs of equal length were previously ordered arbitrarily, so which one a tarball URL matched could differ between runs.
Dependency resolution is faster: package metadata is now filtered once per packument instead of once per dependency edge when minimumReleaseAge is active, and parsed semver versions and ranges are reused instead of re-parsed on every comparison.
Security: pnpm rebuild now refuses a lockfile whose packages key carries a path traversal in the package name (e.g. ../../../escaped@1.0.0), instead of running that package's lifecycle scripts and linking its bins in a directory outside the virtual store. Such a name is rejected with ERR_PNPM_INVALID_DEPENDENCY_NAME.

Platinum Sponsors

Gold Sponsors

`v11.19.0`: pnpm 11.19

Compare Source

Minor Changes

pnpm login no longer requires an interactive terminal when the registry supports web-based login: without a TTY it prints the authentication URL (skipping the QR code and the "Press ENTER to open the URL in your browser" prompt) and polls the registry until the browser approval completes. Only the classic username/password login still fails with ERR_PNPM_LOGIN_NON_INTERACTIVE in a non-interactive terminal.
The save-prefix setting now accepts =: newly added dependencies are saved with an explicit = operator (=1.2.3) instead of the setting being silently treated as the default ^.

Patch Changes

allowBuilds entries can now approve git-hosted packages that pnpm downloads as a tarball, such as github: dependencies (which are fetched from codeload.github.com rather than cloned), by their repository URL without the resolved commit hash. This matches the hashless git+ matching already supported for cloned git dependencies. For example:
```
allowBuilds:
  "foo@git+https://github.com/org/foo.git": true
```
This approves the package whether pnpm clones it or downloads a tarball, so the entry no longer has to be updated every time the pinned commit changes. GitLab and Bitbucket tarball downloads are matched the same way. Approving or denying a specific resolved commit by its full tarball dep path continues to work.
pnpm outdated --include-github-actions no longer blocks on an interactive git credential prompt when a workflow uses a private action repo.
Prevented minimumReleaseAge from replacing latest with a SemVer-greater version than the registry tag target #13034.
Fixed empty bundledDependencies and bundleDependencies arrays causing nondeterministic lockfile changes. See #13123.
The install summary no longer prints (X is available) when the registry's dist-tags.latest is still held back by the active minimumReleaseAge policy. The hint only ever names the actual latest tag, so an immature latest suppresses the hint instead of advertising the version pnpm just refused to install #11698.
pnpm update keeps the explicit = operator of an exact version pin: a dependency saved as =3.5.1 now updates to =3.5.2 instead of the bare 3.5.2. See #13168.
Preserve a workspace dependency's link: entry when a run does not target it — e.g. pnpm update <other-pkg> (with or without --recursive), or a plain install after a root/catalog dependency change — with injectWorkspacePackages, instead of spuriously rewriting it to a peer-suffixed file: protocol. See #10433.
Workspace dependencies declared with a relative path (e.g. "foo": "workspace:../foo") are no longer silently dropped from the workspace projects graph, so --filter selection and the topological order of recursive commands take them into account.

Platinum Sponsors

Gold Sponsors

`v11.18.0`: pnpm 11.18

Compare Source

Minor Changes

Fixed an installed optional dependency being left without one of its own required dependencies. When a package reached through optionalDependencies is installable on the current system but one of its regular dependencies is not, a lockfile-based install skipped that dependency and installed the parent anyway, so importing the parent failed with MODULE_NOT_FOUND. The dependency is now installed, and an install-check warning reports the incompatibility. A dependency is still only skipped when every path to it is optional, or when the package that pulls it in was itself skipped #13286.
pnpm setup now appends PNPM_HOME and the global bin directory to the GitHub Actions environment files (GITHUB_ENV and GITHUB_PATH), so later steps in the same job can run pnpm add --global and other global commands #9191.
Added support for publishConfig.name, which publishes a package under a different name than the one its manifest carries in the workspace. It is for a project whose published name is already taken by a sibling project, which otherwise has to be renamed by a build step just before publishing. Only the published artifact is renamed — dependents, pnpm-lock.yaml, and release tooling keep addressing the project by its manifest name — and the new name reaches the packed manifest, the tarball filename, and everything that addresses the package at the registry: the already-published check of pnpm publish -r, its registry selection, and the release-planning probes of pnpm change status and pnpm version -r #13345.
pnpm self-update no longer takes any instruction from the project it is run in:
- pnpm is fetched through the same trusted registry and auth configuration used when switching pnpm versions, so a project .npmrc or pnpm-workspace.yaml can no longer redirect the download or attach credentials to it, and the project's default .pnpmfile.(c|m)js is no longer loaded. Pnpmfiles from trusted sources (the pnpmfile setting, the global pnpmfile, config dependencies) still apply.
- The minimumReleaseAge settings in pnpm-workspace.yaml no longer affect self-update. They still govern the project's own dependencies; for self-update the cooldown now comes from the built-in default, your global config, a PNPM_CONFIG_* environment variable, or a command-line flag. This fixes self-update failing inside a workspace that raises the cutoff while succeeding everywhere else, and stops a repository from either waiving the cooldown or keeping you on an outdated pnpm by raising it.
- The same applies to the trustPolicy settings and to ci: a project can no longer weaken the trust check that guards the pnpm download, nor re-enable the confirmation prompt that a CI run suppresses.
When self-update refuses a version that is younger than the cutoff, an interactive run now offers to update anyway; non-interactive runs still fail. CI never prompts, even o

✂ Note

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.

renovate Bot force-pushed the renovate/all-minor-patch branch 14 times, most recently from 463b8f4 to 6498410 Compare July 22, 2026 23:58

renovate Bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from 4a9233f to 12f2c04 Compare July 30, 2026 21:48

renovate Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 84abb11 to bb5b7f6 Compare August 1, 2026 11:03

renovate Bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from 839ea2e to 732710a Compare August 8, 2026 14:38

renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 7cb4f51 to e6765ae Compare August 11, 2026 03:01

chore(deps): update all non-major dependencies

496f26a

renovate Bot force-pushed the renovate/all-minor-patch branch from e6765ae to 496f26a Compare August 12, 2026 02:48

Navigation Menu

Uh oh!

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

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

renovate Bot commented Jul 15, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

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

Uh oh!

Release Notes

Bug Fixes

Documentation

Chores

Features

Bug Fixes

Documentation

Chores

v0.29.4: 0.29.4

🚀 Features

🐞 Bugfixes

PostgreSQL 🐘

SQLite 📘

📖 Documentation

📦 CICD & Tooling

⚠️ Breaking Changes

🐤 New Contributors

What's Changed

Bug Fixes

Bug Fixes

Features

v11.20.0: pnpm 11.20

Minor Changes

If you use named registries

New built-in npmjs: alias

Patch Changes

Platinum Sponsors

Gold Sponsors

v11.19.0: pnpm 11.19

Minor Changes

Patch Changes

Platinum Sponsors

Gold Sponsors

v11.18.0: pnpm 11.18

Minor Changes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Jul 15, 2026 •

edited

Loading

`v0.29.4`: 0.29.4

`v11.20.0`: pnpm 11.20

New built-in `npmjs:` alias

`v11.19.0`: pnpm 11.19

`v11.18.0`: pnpm 11.18