[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
wrangler (source)	4.154.0 → 4.155.0

---

Release Notes

cloudflare/workers-sdk (wrangler)

v4.155.0

Compare Source

Minor Changes

• #​16536 a95d647 Thanks @​WalshyDev! - Support remote Analytics Engine bindings in local development

  Setting remote: true on an Analytics Engine dataset now sends writeDataPoint() calls from wrangler dev and the Vite plugin to the real dataset. Without it, writes are still dropped locally.

  {
    "analytics_engine_datasets": [
      {
        "binding": "EVENTS",
        "dataset": "my-dataset",
        "remote": true
      }
    ]
  }

Patch Changes

• #​16526 dba0e81 Thanks @​petebacondarwin! - Render terminal control characters as visible text in tail output

  Pretty tail and remote-preview output now escape control characters in log strings, exceptions and event metadata. Unicode, tabs and multiline logs remain readable, and JSON output keeps the original structured values.

• #​16489 fc57bc0 Thanks @​akshitsinha! - Keep Flagship flag metadata when updating flags

  wrangler flagship flags commands that update an existing flag, such as enable, set, rollout, split, and rules, no longer clear the flag's metadata. wrangler flagship flags pull now copies metadata into the local flag store.

• #​16521 ec6eddd Thanks @​petebacondarwin! - Validate .assetsignore encoding before building asset manifests

  Asset uploads and local development now stop with an actionable user error when .assetsignore is not valid UTF-8 or contains null characters, instead of silently losing its patterns. This also applies to standalone Miniflare and the Wrangler, Vite and Vitest development integrations. Save the file as UTF-8 to continue; UTF-8 files with a byte order mark and intentionally empty files remain supported.

• Updated dependencies [a95d647, c7a3373, c7a3373, c7a3373]:

  • miniflare@5.20261023.2-beta

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

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

---

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

[vercel]

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

Project	Deployment	Actions	Updated
nuxt-better-auth-docs	Ready	Preview	Oct 29, 2026 12:29am UTC

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	better-auth	b75a03c	Commit Preview URL Branch Preview URL	Oct 29 2026, 12:20 AM

[vite-hub]

Session	Status	Started	Duration
Pending	Completed	Not started	—
View session	Waiting	2026-10-29T00:12:49.705Z	2m 26s
View session	Last seen running	2026-10-28T23:11:01.315Z	0s

Latest result

Pull request merged.

Final answers

Session

Pull request merged.

Session

Waiting for GitHub merge request 2430d932-1cb6-4570-bbf0-dd6cd0c87cb3.

View session

Ready to merge. Verified the expected HEAD and dependency diff; no actionable feedback remains. `pnpm lint` and `git diff --check origin/main...HEAD` passed. Wrangler version checks passed in root, docs, and playground, reporting 4.155.0. The host’s frozen install succeeded, and all ten supplied checks passed. No additional repair commit was needed.

Session

Pushed 6dd5b23 with exact-version release-age exceptions for Wrangler and Miniflare. Reproduced the original install failure; the frozen install now passes all 1,902 policy checks. `pnpm lint`, both workspace Wrangler version checks, and `git diff --check` passed. Awaiting CI and automated review.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxtjs/better-auth@679

commit: ef62341

[renovate]

Edited/Blocked Notification

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

⚠️ Warning: custom changes will be lost.