Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 1, 2025

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/workers-types ^4.20251128.0 -> ^4.20251205.0 age confidence
@nuxt/test-utils ^3.20.1 -> ^3.21.0 age confidence
@nuxthub/core (source) 0.10.0-20251128-232930-0579c39 -> 0.10.0-20251206-094240-e4af3d9 age confidence
@shikijs/langs (source) ^3.18.0 -> ^3.19.0 age confidence
@valibot/to-json-schema (source) ^1.3.0 -> ^1.4.0 age confidence
drizzle-orm (source) ^0.44.7 -> ^0.45.0 age confidence
shiki (source) ^3.18.0 -> ^3.19.0 age confidence
vitest (source) ^4.0.14 -> ^4.0.15 age confidence
vue-tsc (source) ^3.1.5 -> ^3.1.6 age confidence
wrangler (source) ^4.51.0 -> ^4.53.0 age confidence

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

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
nuxt-hub/core (@​nuxthub/core)

v0.10.0-20251206-094240-e4af3d9

Compare Source

v0.10.0-20251206-090143-e4af3d9

Compare Source

v0.10.0-20251205-170401-d479a68

Compare Source

v0.10.0-20251205-165908-3bc3f1d

Compare Source

v0.10.0-20251205-151259-d886dbe

Compare Source

v0.10.0-20251205-150936-d886dbe

Compare Source

v0.10.0-20251205-143653-d886dbe

Compare Source

v0.10.0-20251205-142828-f22f976

Compare Source

v0.10.0-20251205-142243-f22f976

Compare Source

v0.10.0-20251205-001323-943b30c

Compare Source

v0.10.0-20251204-154415-81faba6

Compare Source

v0.10.0-20251204-115711-69fe9a9

Compare Source

v0.10.0-20251204-112826-d017eb1

Compare Source

v0.10.0-20251203-230005-e2cb4b3

Compare Source

v0.10.0-20251203-164831-2c81c5d

Compare Source

v0.10.0-20251203-163123-4fab799

Compare Source

v0.10.0-20251203-151842-31ada09

Compare Source

v0.10.0-20251203-150258-31ada09

Compare Source

v0.10.0-20251203-150052-31ada09

Compare Source

v0.10.0-20251203-131637-07be90d

Compare Source

v0.10.0-20251203-131345-07be90d

Compare Source

v0.10.0-20251203-104210-b2d4a1a

Compare Source

v0.10.0-20251203-003036-b2d4a1a

Compare Source

v0.10.0-20251202-162300-b2d4a1a

Compare Source

v0.10.0-20251202-160427-b2d4a1a

Compare Source

v0.10.0-20251202-155333-b2d4a1a

Compare Source

v0.10.0-20251201-194900-b2d4a1a

Compare Source

v0.10.0-20251201-193121-5bc1d8c

Compare Source

v0.10.0-20251201-192858-5bc1d8c

Compare Source

v0.10.0-20251130-111317-0579c39

Compare Source

shikijs/shiki (@​shikijs/langs)

v3.19.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    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)
vitest-dev/vitest (vitest)

v4.0.15

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub
vuejs/language-tools (vue-tsc)

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

v4.52.1

Compare Source

Patch Changes

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! - Remove uses of eval() from the Wrangler bundle

  • #​11284 695fa25 Thanks @​dom96! - Removes duplicate module warnings when vendoring Python packages

  • #​11249 504e258 Thanks @​dario-piotrowicz! - fix: Generalize autoconfig wording

    Generalize the autoconfig wording so that when it doesn't specifically mention "deployment" (since it can be run via wrangler setup or the autoconfig programmatic API)

  • #​11455 d25f7e2 Thanks @​dario-piotrowicz! - Fix autoconfig using absolute paths for static projects

    Running the experimental autoconfig logic through wrangler setup and wrangler deploy --x-autoconfig on a static project results in absolute paths being used. This is incorrect, especially when such paths are being included in the generated wrangler.jsonc. The changes here fix the autoconfig logic to use paths relative to the project's root instead.

    For example given a project located in /Users/usr/projects/sites/my-static-site, before:

    // wrangler.jsonc at /Users/usr/projects/sites/my-static-site
      {
        "$schema": "node_modules/wrangler/config-schema.json",
        "name": "static",
        "compatibility_date": "2025-11-27",
        "observability": {
          "enabled": true
        },
        "assets": {
          "directory": "/Users/usr/projects/sites/my-static-site/public"
        }
      }

    and after:

    // wrangler.jsonc at /Users/usr/projects/sites/my-static-site
      {
        "$schema": "node_modules/wrangler/config-schema.json",
        "name": "static",
        "compatibility_date": "2025-11-27",
        "observability": {
          "enabled": true
        },
        "assets": {
          "directory": "public"
        }
      }
  • #​11484 1cfae2d Thanks @​edmundhung! - Explicitly close FileHandle in wrangler d1 execute to support Node 25

  • #​11383 1d685cb Thanks @​dario-piotrowicz! - Fix: ensure that when a remote proxy session creation fails a hard error is surfaced to the user (both in wrangler dev and in the programmatic API).

    When using remote bindings, either with wrangler dev or via startRemoteProxySession/maybeStartOrUpdateRemoteProxySession the remote proxy session necessary to connect to the remote resources can fail to be created, this might happen if for example you try to set a binding with some invalid values such as:

    MY_R2: {
    	type: "r2_bucket",
    	bucket_name: "non-existent", // No bucket called "non-existent" exists
    	remote: true,
    },

    Before this could go undetected and cause unwanted behaviors such as requests handling hanging indefinitely, now wrangler will instead crash (or throw a hard error ion the programmatic API), clearly indicating that something went wrong during the remote session's creation.

  • #​11366 edf896d Thanks @​ascorbic! - Use correctly-formatted names when displaying detected framework details

  • #​11461 9eaa9e2 Thanks @​dario-piotrowicz! - Update the structure of the configure method of autoconfig frameworks

    Update the signature of the configure function of autoconfig frameworks (AutoconfigDetails#Framework), before they would return a RawConfig object to use to update the project's wrangler config file, now they return an object that includes the RawConfig and that can potentially also hold additional data relevant to the configuration.

  • Updated dependencies [2b4813b, b154de2, 5ee3780, 6e63b57, 71ab562, 5e937c1]:


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
Copy link

vercel bot commented Dec 1, 2025

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

Project Deployment Preview Comments Updated (UTC)
content Error Error Dec 6, 2025 10:03am

@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 1, 2025

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

commit: ba8b90b

@cloudflare-workers-and-pages
Copy link

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

Deploying content with  Cloudflare Pages  Cloudflare Pages

Latest commit: 9d33e03
Status: ✅  Deploy successful!
Preview URL: https://741f19ec.content-f0q.pages.dev
Branch Preview URL: https://renovate-all-minor-patch.content-f0q.pages.dev

View logs

@renovate 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 renovate bot force-pushed the renovate/all-minor-patch branch from d0a572a to 48e2b38 Compare December 1, 2025 13:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 48e2b38 to b5afe7f Compare December 1, 2025 13:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b5afe7f to f2b0ef9 Compare December 1, 2025 20:03
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f2b0ef9 to b173f52 Compare December 2, 2025 03:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b173f52 to 5a341e6 Compare December 2, 2025 06:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5a341e6 to 8e861c1 Compare December 2, 2025 10:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8e861c1 to 87f6efd Compare December 2, 2025 16:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 87f6efd to d2cca3d Compare December 2, 2025 19:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d2cca3d to 40a0c49 Compare December 2, 2025 21:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 40a0c49 to fbc5e50 Compare December 3, 2025 05:26
Copy link

@vercel vercel bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e6d3d82 to 2d07fb2 Compare December 3, 2025 15:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2d07fb2 to 4b45403 Compare December 3, 2025 15:44
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4b45403 to 867a631 Compare December 3, 2025 20:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 867a631 to 36cf312 Compare December 4, 2025 05:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 36cf312 to acd4ea7 Compare December 4, 2025 16:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from acd4ea7 to 16b92c5 Compare December 4, 2025 22:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 16b92c5 to 04b3ad0 Compare December 5, 2025 05:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 04b3ad0 to ebf3265 Compare December 5, 2025 15:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ebf3265 to ba8b90b Compare December 5, 2025 18:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ba8b90b to f96c066 Compare December 6, 2025 04:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant