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

renovate · 2025-12-01T08:53:59Z

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@cloudflare/workers-types	`^4.20251128.0` -> `^4.20251209.0`
@nuxt/test-utils	`^3.20.1` -> `^3.21.0`
@nuxthub/core (source)	`0.10.0-20251128-232930-0579c39` -> `0.10.0-20251209-004424-89ff422`
@shikijs/langs (source)	`^3.18.0` -> `^3.19.0`
@types/bun (source)	`^1.3.3` -> `^1.3.4`
@types/node (source)	`^24.10.1` -> `^24.10.2`
@valibot/to-json-schema (source)	`^1.3.0` -> `^1.4.0`
drizzle-orm (source)	`^0.44.7` -> `^0.45.0`
pnpm (source)	`10.24.0` -> `10.25.0`
shiki (source)	`^3.18.0` -> `^3.19.0`
vitest (source)	`^4.0.14` -> `^4.0.15`
vue-tsc (source)	`^3.1.5` -> `^3.1.8`
wrangler (source)	`^4.51.0` -> `^4.53.0`

Release Notes

cloudflare/workerd (@cloudflare/workers-types)

`v4.20251209.0`

Compare Source

`v4.20251205.0`

Compare Source

nuxt/test-utils (@nuxt/test-utils)

`v3.21.0`

Compare Source

3.21.0 is the next minor release.

👉 Changelog

compare changes

🚀 Enhancements

runtime-utils: Support rerender behavior in renderSuspended (#1466)
runtime-utils: Support once option in registerEndpoint (#1475)
runtime-utils: Support css modules in mount + render helpers (#1464)
runtime-utils: Pass app context across in mount + render helpers (#1477)
runtime-utils: Support mocked target arguments in mockNuxtImport (#1492)

🩹 Fixes

runtime: Remove redefinition of $fetch.create (#1471)
runtime-utils: Pass non-enumerable globalProperties in mount + render helpers (#1476)
module: Include vitest config in node project (#1497)
runtime-utils: Improve mount + render helpers (#1483)
Revert to @nuxt/kit v3 for bridge support (#1498)

🏡 Chore

Move built dep configuration -> workspace file (d936cb465)
Update pnpm to 10.21 and enable trust policy (ed6ff050d)
Revert pnpm trust policy and restore provenance action (b034f0a5e)
Remove spurious globby dependency (eba19d16b)
Remove export (2a88683bd)
Remove @nuxt/kit from peer dependencies (b80ca5ea8)
Add back @nuxt/kit as peer dep (5c126e1af)
Bump vite-node to v5 (3322919c2)

🤖 CI

Rebuild better-sqlite3 on windows (9fdaf3824)

❤️ Contributors

Daniel Roe (@danielroe)
yamachi4416 (@yamachi4416)
Ryota Watanabe (@wattanx)

nuxt-hub/core (@nuxthub/core)

shikijs/shiki (@shikijs/langs)

`v3.19.0`

Compare Source

🚀 Features

Support rootStyle: false option - by @khushthecoder and @antfu in #1184 (baf9a)
transformers:
- Add classActiveCode option to notation transformers - by @GreenHacker420 in #1171 (a6a44)
- Add transformerRemoveComments - by @Bitshifter-9, Copilot, @crazylogic03 and @antfu in #1144 (f2ee3)
twoslash:
- Add context parameter to filter option - by @siddu-09 in #1173 (ac7f5)

🐞 Bug Fixes

Add typesVersions for legacy resolution support - by @khushthecoder in #1179 (100b7)
core: Check embeddedLanguages in registry dependency check - by @vamsi2246 in #1178 (6ad16)
monaco: Correctly handle sparse color map updates - by @wcr-karan in #1169 (38c7f)

View changes on GitHub

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

`v0.45.0`

Compare Source

Fixed pg-native Pool detection in node-postgres transactions
Allowed subqueries in select fields
Updated typo algorythm => algorithm
Fixed $onUpdate not handling SQL values (fixes #2388, tests implemented by L-Mario564 in #2911)
Fixed pg mappers not handling Date instances in bun-sql:postgresql driver responses for date, timestamp types (fixes #4493)

pnpm/pnpm (pnpm)

`v10.25.0`

Compare Source

vitest-dev/vitest (vitest)

`v4.0.15`

Compare Source

🚀 Experimental Features

cache: Add opt-out on a plugin level, fix internal root cache - by @sheremet-va in #9154 (a68f7)
reporters: Print import duration breakdown - by @sheremet-va in #9105 (122ff)

🐞 Bug Fixes

Keep built-in id as is in bun and deno - by @sheremet-va in #9117 (075ab)
Use optimizeDeps.rolldownOptions to fix depreated warning + fix ssr.external: true - by @hi-ogawa in #9121 (fd8bd)
Fix external behavior with deps.optimizer - by @hi-ogawa in #9125 (4c754)
Very minor typo in "Chrome DevTools Protocol" - by @HowToTestFrontend in #9146 (20997)
browser: Run toMatchScreenshot only once when used with expect.element - by @macarie in #9132 (0d2e7)
coverage: Istanbul provider to not break source maps - by @AriPerkkio in #9040 (e4ca9)
deps: Update dependency tinyexec to v1 - in #9122 (fd786)
docs: Remove --browser.provider from docs - by @sheremet-va in #9115 (120b3)
expect: Preserve currentTestName in extended matchers - by @macarie in #9106 (e4345)
pool: Terminate workers on CTRL+c forceful exits - by @AriPerkkio in #9140 (d57d8)
reporters: Show project in github reporter - by @sheremet-va in #9138 (bb65e)
spy: Do not mock overriden method, if parent was automocked - by @sheremet-va in #9116 (1a246)
web-worker: MessagePort objects passed to Worker.postMessage work when clone === "native" - by @whitphx in #9118 (deee8)

View changes on GitHub

vuejs/language-tools (vue-tsc)

`v3.1.8`

Compare Source

`v3.1.7`

Compare Source

`v3.1.6`

Compare Source

Features

feat(vscode): add settings to enable per-block formatting (#5784) - Thanks to @serkodev!
feat(language-service): enhanced component auto import (#5790)
feat(component-meta): add component name and description fields (#5797)
feat(typescript-plugin): add support for template "Add Import" quick fix (#5799) - Thanks to @serkodev!
feat(typescript-plugin): mapping JSDoc informations from <script setup> (#5805)
feat(vscode): support tsdk path for Eclipse Theia (#5806) - Thanks to @serkodev!

Bug Fixes

fix(language-service): ignore intrinsic elements when detect tag name casing (#5771)
fix(language-core): createParsedCommandLineByJson parsed incorrect options since v3.1.5 (#5768 (comment))
fix(vscode): make vue.server.path compatible with Windows (#5772)
fix(vscode): analyze interpolation highlight ranges based on AST (#5777)
fix(vscode): sync latest vscode html language configuration (#5740)
fix(language-core): enhance getVIfNode to support v-else-if directives (#5765) - Thanks to @serkodev!
fix(language-core): generate {} instead of its string value for style="..." (#5781) - Thanks to @KazariEX!
fix(language-core): v-bind="$attrs" loses navigation when inferTemplateDollarAttrs is disabled (#5783)
fix(language-service): skip const props = completion in StringLiteral (#5786)
fix(language-core): unable to get completion for the second scoped class name
fix(language-service): format components with HTML void-element names (#5788) - Thanks to @serkodev!
fix(language-service): properly handle promise when resolving CSS links (#5785)
fix(language-core): infer $el type for generic components using inferComponentDollarEl (#5794)
fix(language-core): ensure <script> content generates before <script setup> (#5795)
fix(language-core): remove bypassDefineComponent hack for better JS support (#4876) (#5379)
fix(language-core): Prettify<T> caused generic props gets inferred as unknown (#5667) - Thanks to @so1ve!
fix(vscode): handle leading < as operator in SFC scripts (#5801) - Thanks to @serkodev!
fix(vscode): patch isTypeScriptDocument in VSCode for typescript.preferences.autoImportSpecifierExcludeRegexes config support (#5364)
fix(language-core): ensure type consistency for optional boolean props (#5803)
fix(language-core): add compatibility for vapor attr (#5496)
fix(language-core): AST fault tolerance for key binding on template (#5807)

Performance

perf(language-core): reuse ts asts for :class - Thanks to @KazariEX!

Other Changes

Revert "refactor(typescript-plugin): remove go to definition trick for auto imported components (#5733)"
docs(typescript-plugin): update Neovim configuration link (#5775) - Thanks to @AlexVagrant!
refactor(language-core): normalize template AST (#5782)
refactor(language-core): split style codegen (#5787)
refactor(language-core): remove debugger from virtual code for tsslint compatibility
refactor(language-core): remove legacy navigation support in ref="xxx"
refactor(language-core): reduce codegen options (#5804)
refactor(component-meta): deprecated rawType and __internal__.tsLs (#5808)
chore: update volar to 2.4.26
- feat: fallback resolution mode for createResolveModuleName (volarjs/volar.js#293) (#5644) - Thanks to @serkodev!

cloudflare/workers-sdk (wrangler)

`v4.53.0`

Compare Source

Minor Changes

#11500 af54c63 Thanks @dario-piotrowicz! - Add new autoconfig_summary field to the deploy output entry

This change augments wrangler deploy output being printed to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH to also include a new autoconfig_summary field containing the possible summary details for the autoconfig process (the field is undefined if autoconfig didn't run).

Note: the field is experimental and could change while autoconfig is not GA
#11477 9988cc9 Thanks @ascorbic! - Support Nuxt in autoconfig
#11472 ce295bf Thanks @dario-piotrowicz! - Support Qwik projects in autoconfig
#10937 9514c9a Thanks @ReppCodes! - Add support for "targeted" placement mode with region, host, and hostname fields

This change adds a new mode to placement configuration. You can specify one of the following fields to target specific external resources for Worker placement:
- region: Specify a region identifier (e.g., "aws:us-east-1") to target a region from another cloud service provider
- host: Specify a host with (required) port (e.g., "example.com:8123") to target a TCP service
- hostname: Specify a hostname (e.g., "example.com") to target an HTTP resource
These fields are mutually exclusive - only one can be specified at a time.

Example configuration:
```
[placement]
host = "example.com:8123"
```
#11498 ac861f8 Thanks @penalosa! - Add React Router support in autoconfig
#11506 79d30d4 Thanks @vicb! - Set the target JS version to ES2024

Patch Changes

#11393 45480b1 Thanks @alsuren! - improved --help text for wrangler d1 subcommands
#11523 94c67e8 Thanks @jamesopstad! - fix: types from @cloudflare/workers-utils not being exported correctly from Wrangler
#11483 f550b62 Thanks @edmundhung! - stop running npm install with --legacy-peer-deps flag when setting up a project
Updated dependencies [819e287, 56e78c8, 0aa959a]:
- @cloudflare/unenv-preset@2.7.13
- miniflare@4.20251202.1

`v4.52.1`

Compare Source

Patch Changes

#11504 7e80340 Thanks @dario-piotrowicz! - Fix wrangler deploy failing for new workers containing environment variables or bindings
Updated dependencies [59534ba]:
- miniflare@4.20251202.0

`v4.52.0`

Compare Source

Minor Changes

#11416 abe49d8 Thanks @dario-piotrowicz! - Remove the wrangler deploy's --x-remote-diff-check experimental flag

The remote diffing feature has been enabled by default for a while and its functionality is stable, as a result the experimental flag (only available for option-out of the feature right now) has been removed.
#11408 f29e699 Thanks @ascorbic! - Export unstable helpers useful for generating wrangler config
#11389 2342d2f Thanks @dario-piotrowicz! - Improve the wrangler deploy flow to also check for potential overrides of secrets.

Now when you run wrangler deploy Wrangler will check the remote secrets for your workers for conflicts with the names of the bindings you're about to deploy. If there are conflicts, Wrangler will warn you and ask you for your permission before proceeding.
#11375 9a1de61 Thanks @penalosa! - Support TanStack Start in autoconfig
#11360 6b38532 Thanks @emily-shen! - Containers: Allow users to directly authenticate external image registries in local dev

Previously, we always queried the API for stored registry credentials and used those to pull images. This means that if you are using an external registry (ECR, dockerhub) then you have to configure registry credentials remotely before running local dev.

Now you can directly authenticate with your external registry provider (using docker login etc.), and Wrangler or Vite will be able to pull the image specified in the containers.image field in your config file.

The Cloudflare-managed registry (registry.cloudflare.com) currently still does not work with the Vite plugin.
#11009 e4ddbc2 Thanks @dario-piotrowicz! - Allow users to provide an account_id as part of the WorkerConfigObject they pass to maybeStartOrUpdateRemoteProxySession
#11478 2aec2b4 Thanks @dario-piotrowicz! - Support SolidStart in autoconfig
#11330 5a873bb Thanks @dario-piotrowicz! - Support Angular projects in autoconfig
#11449 e7b690b Thanks @penalosa! - Delegate generation of HTTPS certificates to Miniflare
#11448 2b4813b Thanks @edmundhung! - Bumps esbuild version to 0.27.0
#11335 c47ad11 Thanks @dario-piotrowicz! - Support internal-only undocumented cross_account_grant service binding property
#11346 a977701 Thanks @penalosa! - We're soon going to make backend changes that mean that wrangler dev --remote sessions will no longer have an associated inspector connection. In advance of these backend changes, we've enabled a new wrangler tail-based logging strategy for wrangler dev --remote. For now, you can revert to the previous logging strategy with wrangler dev --remote --no-x-tail-logs, but in future it will not be possible to revert.

The impact of this will be that logs that were previously available via devtools will now be provided directly to the Wrangler console and it will no longer be possible to interact with the remote Worker via the devtools console.

Patch Changes

#11397 b154de2 Thanks @vicb! - Use more workerd native modules

Node modules punycode, trace_events, cluster, wasi, and domains will be used when enabled
via a compatibility flag or by default when the compatibility date is greater or equal to 2025-12-04.
#11452 76f0540 Thanks [@penalosa](https://r

Configuration

📅 Schedule: Branch creation - "on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

vercel · 2025-12-01T08:54:02Z

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

Project	Deployment	Preview	Comments	Updated (UTC)
content	Error			Dec 9, 2025 2:45am

pkg-pr-new · 2025-12-01T08:56:18Z

npm i https://pkg.pr.new/@nuxt/content@3628

commit: ecd5dff

cloudflare-workers-and-pages · 2025-12-01T08:58:08Z

Deploying content with Cloudflare Pages

Latest commit:	`ecd5dff`
Status:	✅ Deploy successful!
Preview URL:	https://cbdb4eaa.content-f0q.pages.dev
Branch Preview URL:	https://renovate-all-minor-patch.content-f0q.pages.dev

View logs

vercel

Additional Suggestion:

The @nuxthub/core nightly build version in this example is not updated to match the version updated in docs/package.json and playground/package.json. This creates an inconsistency across the monorepo.

View Details

📝 Patch Details

diff --git a/examples/i18n/package.json b/examples/i18n/package.json
index a3bff14c..a1091441 100644
--- a/examples/i18n/package.json
+++ b/examples/i18n/package.json
@@ -11,7 +11,7 @@
   "dependencies": {
     "@nuxt/content": "latest",
     "@nuxt/ui": "^4.1.0",
-    "@nuxthub/core": "npm:@nuxthub/core-nightly@0.10.0-20251128-232930-0579c39",
+    "@nuxthub/core": "npm:@nuxthub/core-nightly@0.10.0-20251203-003036-b2d4a1a",
     "@nuxtjs/i18n": "^10.2.0",
     "nuxt": "^4.2.1"
   }

Analysis

Inconsistent @nuxthub/core nightly build version in examples/i18n/package.json

What fails: The examples/i18n starter uses outdated nightly build version 0.10.0-20251128-232930-0579c39 while docs/package.json and playground/package.json were updated to 0.10.0-20251203-003036-b2d4a1a

How to reproduce:

grep "@nuxthub/core" examples/i18n/package.json
grep "@nuxthub/core" docs/package.json  
grep "@nuxthub/core" playground/package.json

Result: examples/i18n shows outdated version (2025-11-28) while docs and playground show newer version (2025-12-03)

Expected: All three example/documentation packages should use the same nightly build version to maintain consistency across the monorepo

Fixed: Updated examples/i18n/package.json line 14 from 0.10.0-20251128-232930-0579c39 to 0.10.0-20251203-003036-b2d4a1a

vercel

Additional Suggestion:

The @nuxthub/core nightly version in examples/i18n/package.json was not updated to match the version updates made in docs/package.json and playground/package.json.

View Details

📝 Patch Details

diff --git a/examples/i18n/package.json b/examples/i18n/package.json
index 7df0525e..d98370eb 100644
--- a/examples/i18n/package.json
+++ b/examples/i18n/package.json
@@ -11,7 +11,7 @@
   "dependencies": {
     "@nuxt/content": "latest",
     "@nuxt/ui": "^4.2.1",
-    "@nuxthub/core": "npm:@nuxthub/core-nightly@0.10.0-20251128-232930-0579c39",
+    "@nuxthub/core": "npm:@nuxthub/core-nightly@0.10.0-20251206-135637-292b595",
     "@nuxtjs/i18n": "^10.2.1",
     "nuxt": "^4.2.1"
   }

Analysis

Outdated @nuxthub/core-nightly version in examples/i18n/package.json

What fails: The examples/i18n package.json has an outdated nightly version of @nuxthub/core compared to docs and playground directories, causing version mismatch in the monorepo workspace.

How to reproduce:

# Check versions across workspace packages
grep "@nuxthub/core-nightly" examples/i18n/package.json docs/package.json playground/package.json

Result:

examples/i18n/package.json used: 0.10.0-20251128-232930-0579c39
docs/package.json uses: 0.10.0-20251206-135637-292b595
playground/package.json uses: 0.10.0-20251206-135637-292b595

Expected: All packages in the monorepo workspace should use the same version of @nuxthub/core-nightly to ensure consistency and prevent dependency resolution issues. The examples/i18n package should match the updated version used in docs and playground.

vercel

Additional Suggestion:

The @nuxthub/core version in examples/i18n/package.json was not updated to match the version used in docs/package.json and playground/package.json, creating a version inconsistency in the lockfile.

View Details

📝 Patch Details

diff --git a/examples/i18n/package.json b/examples/i18n/package.json
index 7df0525e..e3f299e2 100644
--- a/examples/i18n/package.json
+++ b/examples/i18n/package.json
@@ -11,7 +11,7 @@
   "dependencies": {
     "@nuxt/content": "latest",
     "@nuxt/ui": "^4.2.1",
-    "@nuxthub/core": "npm:@nuxthub/core-nightly@0.10.0-20251128-232930-0579c39",
+    "@nuxthub/core": "npm:@nuxthub/core-nightly@0.10.0-20251209-004424-89ff422",
     "@nuxtjs/i18n": "^10.2.1",
     "nuxt": "^4.2.1"
   }

Analysis

Version inconsistency in @nuxthub/core across examples packages

What fails: The examples/i18n/package.json file specifies an outdated @nuxthub/core version (0.10.0-20251128-232930-0579c39) that was not updated in the latest dependency update, while docs/package.json and playground/package.json both reference the newer version (0.10.0-20251209-004424-89ff422).

How to reproduce:

# Check the version in examples/i18n/package.json:
grep "@nuxthub/core" examples/i18n/package.json

# Compare with docs:
grep "@nuxthub/core" docs/package.json

# Compare with playground:
grep "@nuxthub/core" playground/package.json

Result: The pnpm-lock.yaml file maintains entries for both versions of @nuxthub/core-nightly, causing lock file bloat and version resolution complexity. This was caused by commit ecd5dff ("chore(deps): update all non-major dependencies") which updated docs/package.json and playground/package.json but did not include examples/i18n/package.json in the update.

Expected: All packages in the monorepo workspace (configured in pnpm-workspace.yaml with examples/*) should have their @nuxthub/core dependency pinned to the same version to maintain consistency and minimize lock file complexity.

Fixed by: Updated examples/i18n/package.json line 14 to match the version in docs/package.json and playground/package.json.

vercel bot deployed to Preview December 1, 2025 08:58 View deployment

renovate bot changed the title ~~chore(deps): update all non-major dependencies to ^3.17.1~~ chore(deps): update all non-major dependencies Dec 1, 2025

renovate bot force-pushed the renovate/all-minor-patch branch from d0a572a to 48e2b38 Compare December 1, 2025 13:22

vercel bot deployed to Preview December 1, 2025 13:26 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 48e2b38 to b5afe7f Compare December 1, 2025 13:46

vercel bot deployed to Preview December 1, 2025 13:50 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from b5afe7f to f2b0ef9 Compare December 1, 2025 20:03

vercel bot deployed to Preview December 1, 2025 20:07 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from f2b0ef9 to b173f52 Compare December 2, 2025 03:40

vercel bot deployed to Preview December 2, 2025 03:44 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from b173f52 to 5a341e6 Compare December 2, 2025 06:49

vercel bot deployed to Preview December 2, 2025 06:53 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 5a341e6 to 8e861c1 Compare December 2, 2025 10:55

vercel bot deployed to Preview December 2, 2025 10:59 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 8e861c1 to 87f6efd Compare December 2, 2025 16:02

vercel bot deployed to Preview December 2, 2025 16:06 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 87f6efd to d2cca3d Compare December 2, 2025 19:15

vercel bot deployed to Preview December 2, 2025 19:19 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from d2cca3d to 40a0c49 Compare December 2, 2025 21:08

vercel bot deployed to Preview December 2, 2025 21:12 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 40a0c49 to fbc5e50 Compare December 3, 2025 05:26

vercel bot reviewed Dec 3, 2025

View reviewed changes

vercel bot deployed to Preview December 3, 2025 05:30 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from fbc5e50 to 8fb71ce Compare December 3, 2025 09:24

vercel bot had a problem deploying to Preview December 3, 2025 09:25 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 8fb71ce to e6d3d82 Compare December 3, 2025 10:40

vercel bot had a problem deploying to Preview December 3, 2025 10:40 Failure

vercel bot had a problem deploying to Preview December 4, 2025 16:30 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from acd4ea7 to 16b92c5 Compare December 4, 2025 22:15

vercel bot had a problem deploying to Preview December 4, 2025 22:17 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 16b92c5 to 04b3ad0 Compare December 5, 2025 05:51

vercel bot had a problem deploying to Preview December 5, 2025 05:53 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 04b3ad0 to ebf3265 Compare December 5, 2025 15:05

vercel bot had a problem deploying to Preview December 5, 2025 15:07 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from ebf3265 to ba8b90b Compare December 5, 2025 18:55

vercel bot had a problem deploying to Preview December 5, 2025 18:57 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from ba8b90b to f96c066 Compare December 6, 2025 04:06

vercel bot had a problem deploying to Preview December 6, 2025 04:08 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from f96c066 to 9d33e03 Compare December 6, 2025 10:01

vercel bot had a problem deploying to Preview December 6, 2025 10:03 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 9d33e03 to bbeac5c Compare December 6, 2025 14:56

vercel bot had a problem deploying to Preview December 6, 2025 14:57 Failure

vercel bot reviewed Dec 6, 2025

View reviewed changes

renovate bot force-pushed the renovate/all-minor-patch branch from bbeac5c to 4bc057e Compare December 6, 2025 22:47

vercel bot had a problem deploying to Preview December 6, 2025 22:48 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 4bc057e to a4592d1 Compare December 7, 2025 18:45

vercel bot had a problem deploying to Preview December 7, 2025 18:47 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from a4592d1 to 3e9ab59 Compare December 7, 2025 22:27

vercel bot had a problem deploying to Preview December 7, 2025 22:29 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 3e9ab59 to 6d5c1b8 Compare December 8, 2025 11:13

vercel bot had a problem deploying to Preview December 8, 2025 11:15 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 6d5c1b8 to 043ce26 Compare December 8, 2025 16:02

vercel bot had a problem deploying to Preview December 8, 2025 16:04 Failure

chore(deps): update all non-major dependencies

ecd5dff

renovate bot force-pushed the renovate/all-minor-patch branch from 043ce26 to ecd5dff Compare December 9, 2025 02:44

vercel bot had a problem deploying to Preview December 9, 2025 02:45 Failure

vercel bot reviewed Dec 9, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

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

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

renovate bot commented Dec 1, 2025 •

edited

Loading

Uh oh!

vercel bot commented Dec 1, 2025 •

edited

Loading

Uh oh!

pkg-pr-new bot commented Dec 1, 2025 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages bot commented Dec 1, 2025 •

edited

Loading

Uh oh!

vercel bot left a comment

Uh oh!

vercel bot left a comment

Uh oh!

vercel bot left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

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

Are you sure you want to change the base?

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

Conversation

renovate bot commented Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

👉 Changelog

🚀 Enhancements

🩹 Fixes

🏡 Chore

🤖 CI

❤️ Contributors

🚀 Features

🐞 Bug Fixes

🚀 Experimental Features

🐞 Bug Fixes

Features

Bug Fixes

Performance

Other Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

vercel bot commented Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pkg-pr-new bot commented Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cloudflare-workers-and-pages bot commented Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying content with Cloudflare Pages

Uh oh!

vercel bot left a comment

Choose a reason for hiding this comment

Analysis

Inconsistent @nuxthub/core nightly build version in examples/i18n/package.json

Uh oh!

vercel bot left a comment

Choose a reason for hiding this comment

Analysis

Outdated @nuxthub/core-nightly version in examples/i18n/package.json

Uh oh!

vercel bot left a comment

Choose a reason for hiding this comment

Analysis

Version inconsistency in @nuxthub/core across examples packages

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Dec 1, 2025 •

edited

Loading

vercel bot commented Dec 1, 2025 •

edited

Loading

pkg-pr-new bot commented Dec 1, 2025 •

edited

Loading

cloudflare-workers-and-pages bot commented Dec 1, 2025 •

edited

Loading