[dependabot]

Bumps the minor-and-patch group with 2 updates in the / directory: astro and wrangler.

Updates astro from 7.4.3 to 7.4.4

Release notes

Sourced from astro's releases.

astro@7.4.4

Patch Changes

• #18344 df838da Thanks @​edmundhung! - Allows astro add to configure tagged versions of official adapters

astro@7.4.4-beta.0

Patch Changes

• #18539 db62f3b Thanks @​matthewp! - Allows astro add to configure tagged versions of official adapters

Changelog

Sourced from astro's changelog.

7.4.4

Patch Changes

• #18344 df838da Thanks @​edmundhung! - Allows astro add to configure tagged versions of official adapters

Commits

• 883e672 [ci] release (#18540)
• df838da astro add: configure tagged official adapters (#18344)
• See full diff in compare view

Updates wrangler from 4.151.2 to 4.156.0

Release notes

Sourced from wrangler's releases.

wrangler@4.156.0

Minor Changes

• #16532 25802bc Thanks @​simonha9! - Allow the experimental wrangler d1 insights command to run across every D1 database in the account

  The 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 databaseId field.

Patch Changes

• #16369 ec0bea4 Thanks @​MattieTK! - Stop autoconfig in non-interactive runs when a project root holds both static files and a Pages functions directory

  When a project without a detected framework has a functions directory, 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 a functions directory 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 b4653b4 Thanks @​MattieTK! - Write a protective .assetsignore when autoconfig uses the project root as the static assets directory

  Autoconfig is meant to write an .assetsignore when 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 .assetsignore was written. A static project with an index.html at its root (for example after wrangler setup or a zero-config wrangler deploy) then uploaded files such as .env, .dev.vars, .git and node_modules as 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 .assetsignore also covers what a Cloudflare Pages upload skips, alongside the existing .wrangler, .dev.vars* and .env* entries: /_worker.js, /_routes.json and /functions at the root (so nested paths such as blog/functions/index.html are still uploaded), node_modules, .git and .DS_Store at any depth, and .npmrc. If an existing .assetsignore only lists a narrower pattern such as .env, .env* is added so that files like .env.production are skipped too. When the project root of an assets-only project contains a Pages functions directory 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 25802bc Thanks @​simonha9! - Fail the experimental wrangler d1 insights command with an actionable error when the GraphQL Analytics API rejects the request

  Previously 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 8b64bec Thanks @​swalker326! - Fix Durable Object self-references in tests and container validation

  Durable Object bindings that explicitly name the Worker itself now resolve to the test runner in @cloudflare/vitest-plugin, for both cloudflare.config.ts and 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 --name or a CI name override preserves the intended Durable Object target.

• Updated dependencies [15fbaed, d8899ac]:

  • miniflare@5.20261023.3-beta

wrangler@4.155.0

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

... (truncated)

Commits

• b1ced56 Version Packages (#16556)
• 8b64bec [config] Fix Durable Object self-references without changing deployment targe...
• 25802bc [wrangler] Run wrangler d1 insights account-wide (#16532)
• b4653b4 [autoconfig] Write a protective .assetsignore when the project root is the as...
• a09957a Version Packages (#16553)
• c7a3373 Revert "Version Packages" (#16554)
• a95d647 [wrangler] Support remote Analytics Engine bindings in local dev (#16536)
• 52315bd Version Packages (#16529)
• dba0e81 [wrangler] Escape terminal controls in tail output (#16526)
• fc57bc0 [miniflare] Enable local Flagship management without Worker bindings (#16489)
• Additional commits viewable in compare view

[meaningfool]

Checked before merging. I merged this PR (d86fffa) into main (ece409c) locally; the merge tree, 5abffe3, is the one GitHub will create. Node 24.22.1, Bun 1.4.4. Content: meaningfool-writing main at 2ab9242.

• Install: bun install --frozen-lockfile passes, giving astro 7.4.4 and wrangler 4.156.0. Running bun install without the flag leaves bun.lock as it is.
• Build: bun run build passes with 62 pages. Compared with a build of main, dist/ is byte-identical apart from the Generated: timestamps in llms.txt and llms-full.txt.
• Tests: bun run test:documents gives 12 passed and 0 failed.
• Deploy: bunx wrangler deploy --dry-run reads the 222 files in dist/ and binds ASSETS, as before.
• Lockfile: Dependabot's Bun wrote the lockfile without the libc fields of the Linux packages, and without hasInstallScript for esbuild and workerd. On Linux, Bun now installs both the glibc and the musl builds of the native packages (sharp, rolldown, lightningcss and others): node_modules grows from 346 MB to 414 MB. Each system loads only its own build, so the site doesn't change. Dependabot will keep writing the lockfile this way, so I left it as it is.

---

Generated by Claude Code