build(deps-dev): bump wrangler from 4.61.1 to 4.105.0

[dependabot]

Bumps wrangler from 4.61.1 to 4.105.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.105.0

Minor Changes

• #14311 34e0cef Thanks @​sherryliu-lsy! - Add Google Artifact Registry support to containers registries configure

  wrangler containers registries configure now recognizes *-docker.pkg.dev (Google Artifact Registry) domains.

  • The Google service account email is the public credential, supplied with --gar-email. It must match the client_email in the service account key.
  • The service account JSON key is the private credential. It is provided via stdin (a file path, raw JSON, or base64) or an interactive prompt (a file path or base64) — never as a CLI flag, so it does not appear in shell history. The key is validated against --gar-email and stored base64-encoded.
  • Secret reuse inherits the existence-first flow: when the target Secrets Store secret already exists, it is reused by reference and the key is not required. In that case the email cannot be verified locally; it is validated against the key when images are pulled.

  <path-to-key>.json | npx wrangler@latest containers registries configure <region>-docker.pkg.dev --gar-email=<service-account-email> --secret-name=Google_Service_Account_JSON_Key

Patch Changes

• #14424 5f40dd5 Thanks @​MattieTK! - Bump am-i-vibing from 0.4.0 to 0.5.0

  This updates the agentic environment detection library to the latest version, which adds detection for the Pi coding agent (earendil-works/pi).

• #14406 3b743c1 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260623.1	1.20260625.1

• #14343 daa5389 Thanks @​th0m! - Use digest-pinned image references for Dockerfile container deploys

  Dockerfile-backed container deploys now use the pushed image digest when deploying the container application. This lets snapshot-enabled container apps pass Cloudchamber validation while keeping local, non-pushed builds and registry image URI deploys unchanged.

• #14394 8a5cf8c Thanks @​Partha-Shankar! - fix(d1): escape migrationsTableName and filenames in SQLite queries

  D1 migration commands in both wrangler and @cloudflare/vitest-pool-workers interpolated the migrationsTableName config value and migration filenames directly into SQL strings without any escaping. This meant:

  • A table name such as my"table would produce invalid SQL in CREATE TABLE, SELECT, and INSERT statements, and
  • A migration filename containing an apostrophe (e.g. what's-new.sql) would break the INSERT INTO ... VALUES ('...') statement appended after each migration in wrangler.

  Both identifiers are now properly escaped before interpolation: migrationsTableName is wrapped in double-quotes with internal double-quotes doubled (SQL-standard identifier quoting), and migration filenames used as string literals have their single-quotes doubled before insertion.

• Updated dependencies [3b743c1]:

  • miniflare@4.20260625.0

wrangler@4.104.0

Minor Changes

• #14369 e312dec Thanks @​edmundhung! - Add getEnv() to createTestHarness() Worker handles

... (truncated)

Commits

• 70d97d9 Version Packages (#14401)
• 5f40dd5 [wrangler] Bump am-i-vibing from 0.4.0 to 0.5.0 (#14424)
• 3b743c1 Bump workerd from 1.20260623.1 to 1.20260625.1 in the workerd-and-workers-typ...
• 10543c1 [wrangler] interpolate current date to fix brittle test (#14421)
• 76cc8d6 extremely minor refactor of versions upload/deploy validation (#14400)
• daa5389 Use digest-pinned images for Dockerfile container deploys (#14343)
• 34e0cef CC-7948 Update wrangler CLI to support GAR (#14311)
• 8a5cf8c [wrangler] fix(d1): escape migrationsTableName and filenames in SQLite querie...
• ec856a1 Version Packages (#14370)
• fab565f Bump workerd from 1.20260621.1 to 1.20260623.1 in the workerd-and-workers-typ...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[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	Updated (UTC)
❌ Deployment failed View logs	website	a23b697	Jun 29 2026, 05:54 PM

[deepsource-io]

DeepSource Code Review

We reviewed changes in 37cf81f...a23b697 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade

Security   Reliability   Complexity   Hygiene

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
Code coverage		Jun 29, 2026 6:25p.m.	Review ↗
Secrets		Jun 29, 2026 5:55p.m.	Review ↗
JavaScript		Jun 29, 2026 5:55p.m.	Review ↗

---

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

[github-actions]

This pull request has been marked as stale because it has not had any activity for 30 days. The PR will be closed in 7 days if no further activity occurs.

To keep this PR open, simply add a comment, push new commits, or remove the needs review label. Add the wip label to prevent future stale marking..

Need to rebase or update? Consider rebasing against the latest target branch to show continued development.