fix(deps): update all non-major dependencies#222
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
July 6, 2026 09:00
d7d274d to
a68b758
Compare
Contributor
Author
|
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
July 7, 2026 16:58
f133774 to
9ef068a
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
July 8, 2026 10:57
9ef068a to
b03eed9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^21.0.2→^21.2.1^21.0.2→^21.2.0^10.62.0→^10.64.0^4.1.9→^4.1.10^2.19.2→^2.20.0^0.56.0→^0.58.0^1.71.0→^1.73.011.9.0→11.10.0^3.8.4→^3.9.4^0.22.3→^0.22.4^4.1.9→^4.1.10Release Notes
conventional-changelog/commitlint (@commitlint/cli)
v21.2.1Compare Source
Note: Version bump only for package @commitlint/cli
v21.2.0Compare Source
Features
v21.1.0Compare Source
Features
21.0.2 (2026-05-29)
Bug Fixes
21.0.1 (2026-05-12)
Note: Version bump only for package @commitlint/cli
conventional-changelog/commitlint (@commitlint/config-conventional)
v21.2.0Compare Source
Features
v21.1.0Compare Source
Note: Version bump only for package @commitlint/config-conventional
21.0.2 (2026-05-29)
Note: Version bump only for package @commitlint/config-conventional
21.0.1 (2026-05-12)
Note: Version bump only for package @commitlint/config-conventional
getsentry/sentry-javascript (@sentry/node)
v10.64.0Compare Source
Important Changes
feat(cloudflare): Add
nodejs_compatentrypoint (#21881)The Cloudflare SDK now ships a dedicated
@sentry/cloudflare/nodejs_compatentrypoint for Workers running with thenodejs_compatflag. This entrypoint unlocks Node SDK features on Cloudflare, including theprismaIntegration(#21882) and AI v7 support for thevercelAiIntegration(#21917).This entrypoint is a drop-in replacement, so you can switch your imports from
@sentry/cloudflaredirectly to@sentry/cloudflare/nodejs_compat. To use it, your Worker must set thenodejs_compatcompatibility flag inwrangler.toml/wrangler.jsonc. This will become the default entrypoint in v11.feat: Use Sentry's minimal OpenTelemetry tracer provider by default (#21666, #21680, #21842)
The Node SDK now registers Sentry's own minimal
SentryTracerProviderby default, which creates native Sentry spans directly instead of routing them through the full OpenTelemetry SDK span pipeline. This reduces overhead for the common case where you don't need the full OpenTelemetry tracing stack.If you rely on OpenTelemetry SDK features that the minimal provider doesn't support, you can opt out and fall back to the full OpenTelemetry
BasicTracerProviderby settingopenTelemetryBasicTracerProvider: truein yourSentry.init()options. Providing customopenTelemetrySpanProcessorsalso forces the full provider automatically.Other Changes
sentry.trace_lifecycleattribute (#21850)Middleware.executeroot spans on Node.js runtime (#22013)onBeforeLoad/onResolved(#21975)Internal Changes
app-idwithclient-idin GH workflows (#21914)@opentelemetry/instrumentation-ioredisto orchestrion (#21849)@opentelemetry/instrumentation-hapito orchestrion (#21866)@sentry/conventionsto@sentry/coreand align versions (#21855)@sentry/conventionsand vendor remaining semantic conventions (#21893)injectDiagnosticsfor orchestrion marker (#21987)additionalDependencies(#21878)Work in this release was contributed by @codr and @zenato. Thank you for your contribution!
Bundle size 📦
v10.63.0Compare Source
url.fullattribute to resource spans (#21846)extendIntegrationmethod (#21759)isTracingSuppressedto the async context strategy (#21785)fastifyIntegration(#21706)sentry.status.messageattribute (#21811)Internal Changes
fastifyIntegration(#21706)spanStreamingIntegrationsetup intoServerRuntimeClient(#21814)mysqlinstrumentation with orchestrion bundler plugin (#21782)Work in this release was contributed by @suzunn. Thank you for your contribution!
vitest-dev/vitest (@vitest/coverage-v8)
v4.1.10Compare Source
🐞 Bug Fixes
View changes on GitHub
HugoRCD/evlog (evlog)
v2.20.0Compare Source
What's Changed
Features 🚀
evlog/eveintegration by @HugoRCD in #399Bug Fixes 🐞
Full Changelog: https://github.com/HugoRCD/evlog/compare/evlog@2.19.2...evlog@2.20.0
oxc-project/oxc (oxfmt)
v0.58.0Compare Source
v0.57.0Compare Source
oxc-project/oxc (oxlint)
v1.73.0Compare Source
🚀 Features
a2c97f3linter/unicorn: Implementexplicit-timer-delayrule (#23612) (Mikhail Baev)85735cblinter/unicorn: Implementno-confusing-array-withrule (#23638) (Shekhucb4fbb9linter/eslint: Implement no-unreachable-loop rule (#23975) (Todor Andonov)dc32112linter/eslint/no-constant-binary-expression: Check relational comparisons (#24088) (camc314)d963967linter/unicorn/no-array-sort: AddallowAfterSpreadoption (#24043) (Boshen)0a75682linter: Add per-rule timings for type-aware linting (#22488) (camchenry)743e222linter/react: AdddisallowedValuesoption forforbid-dom-propsrule (#23970) (Mikhail Baev)🐛 Bug Fixes
bdb51c7linter/jest/prefer-ending-with-an-expect: Validate config patterns (#24122) (camc314)45d607dlinter/react/forbid-component-props: Make allow/disallow lists optional in schema (#24024) (Boshen)v1.72.0Compare Source
🚀 Features
1c8f50clinter: Add schema foreslint/no-restricted-import(#23642) (Sysix)🐛 Bug Fixes
742be36refactor/node/handle-callback-err: Reject invalid regex config (#23740) (camc314)pnpm/pnpm (pnpm)
v11.10.0Compare Source
Minor Changes
e2e3c81: Added theissuescommand as an alias ofbugs, sopnpm issuesopens the package's bug tracker URL in the browser.8491f8e: Added theprefixcommand which prints the current package prefix directory (or global prefix directory if-g/--globalis used).3425e80: Added an_authsetting for configuring registry authentication as a single structured (URL-keyed) value. It can be set in the global pnpm config (config.yaml) or, for CI, via thepnpm_config__authenvironment variable. The env form sidesteps the GitHub Actions / bash / zsh limitation that broke the existingpnpm_config_//host/:_authToken=…form (env var names containing/,:, or.are silently dropped). Closes #12314.The value is keyed by registry URL so each secret is explicitly bound to the host that may receive it. Registry URL keys must use
httporhttpsand must not include credentials, query strings, or fragments:The equivalent in the global
config.yaml:Within each registry URL,
@means registry-wide/default credentials and package scopes like@orgbind credentials to that scope on the same host. The only supported credential field isauthToken(maps to_authToken/ bearer auth); the deprecatedbasicAuth/username+passwordforms are intentionally not accepted here.Each entry also infers a trusted registry route:
@routes the default registry (andpnpm add <pkg>resolves there), and@orgroutes that scope. Because the credential and destination host arrive in one trusted value, repo-controlledpnpm-workspace.yamlor project.npmrccannot redirect the token to a different host._authis honored only from the env var and the global config — it is ignored in a projectpnpm-workspace.yaml/.npmrc, so repo-controlled config can never supply registry auth. Precedence: CLI flags (--registry,--@​scope:registry) >pnpm_config__auth> globalconfig.yaml_auth>pnpm-workspace.yaml.Both
pnpm_config__auth(lowercase, documented form) andPNPM_CONFIG__AUTH(all-caps, the shell convention some CI runners apply) are honored. If both are set, lowercase wins unless it is empty, in which case uppercase is used. The env var wins over the globalconfig.yaml_authon a conflicting key.tokenHelperis not supported in_auth. Parsing is strict: a malformed value (bad JSON, wrong shape, invalid registry URL or scope, an unsupported credential field) fails fast with an error rather than being silently dropped.Pacquet parity note: the pacquet (Rust) port supports the same single credential field as the TS CLI:
authToken.a33eeec:pnpm self-updateandpackageManagerversion-switching can now install and link pnpm v12 (the Rust port), published with equal content under both thepnpmand@pnpm/exenames on thenext-12dist-tag. Its native binaries ship as@pnpm/exe.<platform>-<arch>packages, which pnpm's built-in installer links directly — no Node.js launcher, so the command pays no Node startup cost. v12 is initialized exactly like@pnpm/exe, including per-platform global-virtual-store hashing. From v12 onward the install converges on the unscopedpnpmpackage (the Rust exe) — even when updating from the SEA@pnpm/exebuild.1dd12bd: When resolving through a pnpr install-accelerator server, pnpm no longer forwards its own upstream registry credentials in the resolve request. Only theAuthorizationheader identifying the caller to pnpr is sent. The pnpr server now selects upstream credentials from its own route policy (operator-configured upstream credential aliases), so private dependencies resolve through a pnpr-managed alias the caller is authorized to use, rather than by sending the client's registry tokens to the server.1e81761: Expose web authenticationauthUrlanddoneUrlin JSON error output when OTP is required in a non-interactive terminal #12724.Patch Changes
2f389d6: Added the Node.js release team's new signing key (Stewart X Addison,655F3B5C1FB3FA8D1A0CA6BDE4A7D232B936D2FD) to the embedded Node.js release keys, so runtimes whoseSHASUMS256.txtis signed by the new releaser verify successfully.acbdb94: Fixed shell tab completion not suggesting workspaces after the-Falias for--filteroption.dcabb78: Fixedpnpm up -r <pkg>bumping unrelated packages that have open semver ranges. Previously, any update mutation nullified the lockfile-derivedpreferredVersionsglobally, so packages with^x.y.zranges could re-resolve to newer compatible versions even though the user only asked to update a specific package. The install layer now always seedspreferredVersionsfrom the lockfile, and caller-supplied preferred versions (such as the vulnerability penalties ofpnpm audit --fix) layer on top of the seed instead of replacing it. The targeted package still bumps: the per-resolveupdateRequestedflag makes the resolver ignore the target's own lockfile pins.Closes #10662.
d539172: Fixed pnpm pack and pnpm publish failing when prepack generates files that are included in the package and postpack cleans them up.be6505a: Hardened global package management:node.exeflavor of a bin, so a stalenode.exeno longer survives onPATHafter uninstall, and a new global install no longer silently overwrites an existingnode.exe.pnpm add -g pnpm@<version>(and@pnpm/exe@<version>) is now rejected like the barepnpmform, pointing topnpm self-update.node_modulespaths, preventing a tampered manifest from escaping the install directory.25c7388: pnpm now rejectsjsr:specifiers whose package name is not a valid npm package name — an empty scope or name (e.g.jsr:@​scope/), path separators inside the name, or any other shapevalidate-npm-package-namerejects — withERR_PNPM_INVALID_JSR_PACKAGE_NAMEinstead of silently converting them into a malformed@jsr/...npm package name.25c7388: pnpm now rejects named-registry specifiers (e.g.gh:) whose package name is not a valid npm package name — an empty scope (e.g.gh:@​/bar), path separators inside the name (e.g.gh:@​scope/../name), or any other shapevalidate-npm-package-namerejects — withERR_PNPM_INVALID_NAMED_REGISTRY_PACKAGE_NAMEinstead of passing the name through to registry URLs and metadata cache file paths.96da7c5: node-gyp'sgyp_main.pyandgypentrypoints are now packed with the executable bit in thepnpmand@pnpm/exetarballs. Without it, building native addons from source could fail with a permission error.99982b9: Sped up resolution and reduced memory use against registries that ignore npm's abbreviated metadata format and always return the full package document (for example, Azure DevOps Artifacts). pnpm now strips such documents down to the abbreviated field set before caching them. Resolution output is unchanged, and registries that honor the abbreviated format (such as the npm registry) pay no extra cost.11a7fdd: Sped up offline and--prefer-offlineresolution on large workspaces (e.g.pnpm dedupe --offline,pnpm install --offline). Package metadata loaded from the local cache is now kept in memory, so each package's metadata is parsed once per command instead of once per dependent that references it.2c7369d:pnpm pack-appnow rejects--entry/pnpm.app.entryand--output-dir/pnpm.app.outputDirvalues that are absolute paths or escape the project directory via..(or a symlink that resolves outside it), and refuses to write the produced executable when its target path already exists as a symlink (or other non-regular file). This prevents a repository-controlledpackage.jsonfrom embedding host files (such as an SSH key) into the produced executable, writing build artifacts outside the project, or overwriting an arbitrary file through a committed symlink. The new error codes areERR_PNPM_PACK_APP_ENTRY_OUTSIDE_PROJECT,ERR_PNPM_PACK_APP_OUTPUT_DIR_OUTSIDE_PROJECT, andERR_PNPM_PACK_APP_OUTPUT_FILE_NOT_REGULAR.When ad-hoc signing macOS targets,
pnpm pack-appnow runs the systemcodesignby absolute path and resolvesldidto a location outside the project, so a repository-controllednode_modules/.binonPATHcannot hijack the signer.ce5d5a5: Relative paths inpatchedDependenciesare now resolved against the lockfile directory when computing patch file hashes, so runningpnpm installfrom a subdirectory no longer fails withENOENTlooking for the patch file in the wrong location #12762.ebb4096:pnpm peersno longer reports a conflict for a missing peer dependency that is ignored viapnpm.peerDependencyRules.ignoreMissing.dcabb78: Fixed a prototype-pollution hazard when seeding preferred versions: a dependency named__proto__in a manifest or inpnpm-lock.yamlcould write throughObject.prototype(or crash the install) while the preferred-versions map was being built. The maps are now null-prototype objects, so crafted package names land as plain keys.f38e696: Hardenedpnpm deploy --forceso it refuses unsafe deploy targets such as workspace roots, parent directories, out-of-workspace paths, and symlinked target parents.806c3ec: pnpm no longer warns about ignored project-level auth settings whenPNPM_CONFIG_NPMRC_AUTH_FILEpoints at the project.npmrc— setting it to that file is an explicit opt-in to trusting it, so auth env variables in it are expanded pnpm/pnpm#12480.991405e: Restore differential rendering (ansi-diff) to fix duplicated output lines introduced by #12351.c121235: Fixed the topological order of--filtered commands (pnpm run,pnpm exec,pnpm publish,pnpm pack,pnpm rebuild) when the selected projects depend on each other only transitively through projects that were not selected. Previously such selected projects could run concurrently or in the wrong order; now a project always runs after the selected projects it transitively depends on, while projects without a real dependency relationship still run concurrently. This now also holds for prod-only filters (--filter-prod), which resolve order through the production dependency graph so transitive production dependencies are respected without pulling back the dev dependencies the filter drops, and for selections that mix--filterwith--filter-prod#8335.d539172:pnpm packandpnpm publishno longer follow a symlinked workspaceLICENSEfile when injecting it into a package that has no license of its own. Following the symlink could pack bytes from outside the workspace into the published tarball.dcabb78: Fixedpnpm up <pkg>producing a different result than a fresh install of the same manifests would. The resolver now distinguishesupdateRequested(true only for packages that match the user's update target) from the broaderupdateflag, and for the targeted package ignores only its own lockfile-derived preferred-version pins — so the target re-resolves exactly as if its lockfile entries were deleted andpnpm installran. Preferred versions a fresh install applies (manifest pins, versions propagated down the dependency chain, and the vulnerability-avoidance penalties ofpnpm audit --fix) stay in effect, so an update never installs duplicate versions that a reinstall from scratch would not reproduce. When a preferred version holds the update target below the newest version its range admits, pnpm now prints a warning explaining that reaching the newer version everywhere requires an override.dcabb78:pnpm update <dep>@​<version>now prints a warning when<dep>is only present as a transitive dependency: the requested version cannot be applied there (updates resolve the target the way a fresh install would), and the warning recommends adding the version topnpm.overridesinstead, which is the mechanism that does pin transitive dependencies. Closes #12744.a6c4d5f: When a dependency cannot be found in the registry (404) or the registry has no matching version, and a workspace project with the same name exists only at non-matching versions, the error now reports the available workspace versions (ERR_PNPM_NO_MATCHING_VERSION_INSIDE_WORKSPACE) instead of the raw registry failure pnpm/pnpm#1379. Other registry failures (authorization, network, server errors) still propagate unchanged. The pacquet (Rust) resolver applies the same behavior.prettier/prettier (prettier)
v3.9.4Compare Source
v3.9.3Compare Source
v3.9.2Compare Source
v3.9.1Compare Source
v3.9.0Compare Source
diff
🔗 Release Notes
v3.8.5Compare Source
rolldown/tsdown (tsdown)
v0.22.4Compare Source
🚀 Features
🐞 Bug Fixes
SOURCEMAP_BROKENwarning - by @ocavue in #982 [(84b7c)](https://redirect.github.com/rolldown/tsdown/coConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.
Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.