Repository navigation
chore(deps): update dev dependencies - #683
Conversation
Latest result Pull request merged. Final answersSession Pull request merged. Session Waiting for GitHub merge request 14c2cc21-14c9-47cf-ba89-53a1e295cb59. Session Pushed 381cff0 to resolve the lockfile merge conflict while preserving both dependency updates. Host frozen installation, lockfile assertions, focused ESLint, CLI version checks, and git diff --check passed. No review findings remain; awaiting CI for the new HEAD. Session Pushed 381cff0 to resolve the lockfile merge conflict while preserving both dependency updates. Host frozen installation, lockfile assertions, focused ESLint, CLI version checks, and git diff --check passed. No review findings remain; awaiting CI for the new HEAD. Session Pushed 381cff0 to resolve the lockfile merge conflict while preserving both dependency updates. Host frozen installation, lockfile assertions, focused ESLint, CLI version checks, and git diff --check passed. No review findings remain; awaiting CI for the new HEAD. Session Pushed 381cff0 to resolve the lockfile merge conflict while preserving both dependency updates. Host frozen installation, lockfile assertions, focused ESLint, CLI version checks, and git diff --check passed. No review findings remain; awaiting CI for the new HEAD. Session Pushed 381cff0 to resolve the lockfile merge conflict while preserving both dependency updates. Host frozen installation, lockfile assertions, focused ESLint, CLI version checks, and git diff --check passed. No review findings remain; awaiting CI for the new HEAD. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
better-auth | 381cff0 | Commit Preview URL Branch Preview URL |
Oct 29 2026, 08:44 PM |
commit: |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This PR contains the following updates:
3.3.13→3.3.144.155.0→4.156.0Release Notes
vuejs/language-tools (vue-tsc)
v3.3.14Compare Source
language-core
__VLS_unwrapto keep literal bindings on TS 7.1 (ce6c1de)neverslot props for dynamic slot names in generic components (7957e7f)$eventparameter of inline handlers explicitly (d3b42a1)@ts-nocheckand/// <reference>effective in script setup (c2e2e6f)language-service
html.customDataconfiguration (3961653)typescript-plugin
Contributors: @johnsoncodehk, @lazerg, @ValentinYoushkevich, @so1ve, @WangKepeople
cloudflare/workers-sdk (wrangler)
v4.156.0Compare Source
Minor Changes
#16532
25802bcThanks @simonha9! - Allow the experimentalwrangler d1 insightscommand to run across every D1 database in the accountThe database name is now optional. With no name, the command returns the top queries across every D1 database in the account, and each result gains a
databaseIdfield.Patch Changes
#16369
ec0bea4Thanks @MattieTK! - Stop autoconfig in non-interactive runs when a project root holds both static files and a PagesfunctionsdirectoryWhen a project without a detected framework has a
functionsdirectory, autoconfig asks whether it is a Cloudflare Pages project. Non-interactive runs (CI and coding agents) assume it is not and continue as a static site. When the static files are in the project root, that deploys the root as static assets, and the Pages Functions (the project's API routes) are not deployed.In that case autoconfig now stops with an error explaining that Pages Functions cannot be migrated automatically yet. For Pages Functions it suggests moving the static files into a subdirectory and deploying with
wrangler pages deploy, or migrating the Functions to a Worker; for afunctionsdirectory that is not Pages Functions, it suggests moving the static files into a subdirectory or adding a configuration file. Projects whose static files are already in a subdirectory, projects detected as Pages or with a detected framework, and interactive runs where the user answers the prompt are unaffected.#16367
b4653b4Thanks @MattieTK! - Write a protective.assetsignorewhen autoconfig uses the project root as the static assets directoryAutoconfig is meant to write an
.assetsignorewhen the project root itself is the assets directory, so that local files are not uploaded as public assets. The check compared the detected output directory, which is relative ("."), with the absolute project path, so it never matched and no.assetsignorewas written. A static project with anindex.htmlat its root (for example afterwrangler setupor a zero-configwrangler deploy) then uploaded files such as.env,.dev.vars,.gitandnode_modulesas public assets.The check now resolves the assets directory that the generated configuration uses and compares it with the project root, so frameworks that set their own build output directory (such as Nuxt or SvelteKit) do not get an unused root
.assetsignore. The generated.assetsignorealso covers what a Cloudflare Pages upload skips, alongside the existing.wrangler,.dev.vars*and.env*entries:/_worker.js,/_routes.jsonand/functionsat the root (so nested paths such asblog/functions/index.htmlare still uploaded),node_modules,.gitand.DS_Storeat any depth, and.npmrc. If an existing.assetsignoreonly lists a narrower pattern such as.env,.env*is added so that files like.env.productionare skipped too. When the project root of an assets-only project contains a Pagesfunctionsdirectory or_worker.js, autoconfig now warns that it will not be deployed, since it is excluded from the assets and not run as server code.#16532
25802bcThanks @simonha9! - Fail the experimentalwrangler d1 insightscommand with an actionable error when the GraphQL Analytics API rejects the requestPreviously the command printed an empty
[]. Rate limit errors now say how long to wait before retrying, and authorization errors name the "Account Analytics: Read" permission the API token needs.#16013
8b64becThanks @swalker326! - Fix Durable Object self-references in tests and container validationDurable Object bindings that explicitly name the Worker itself now resolve to the test runner in
@cloudflare/vitest-plugin, for bothcloudflare.config.tsand Wrangler configuration files. Named Wrangler environments use their effective Worker name, keeping bindings to the base Worker external. Container validation also accepts these self-references, using the effective deployment name to distinguish local and external bindings.Explicit binding targets remain intact during configuration conversion, so deploying with
--nameor a CI name override preserves the intended Durable Object target.Updated dependencies [
15fbaed,d8899ac]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ 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.