Update dependency wretch to v3.0.9

[amitsingh-007]

This PR contains the following updates:

Package	Change	Age	Confidence
wretch (source)	3.0.8 → 3.0.9

---

Release Notes

elbywan/wretch (wretch)

v3.0.9

Compare Source

🎨 Code improvement(s)

• Narrow AbortAddon controller() return type to AbortController (6a83061)

🐛 Bug fix(es)

• Fix .fetchError catching user errors (9a8faad), closes #​318

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
• 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 this update again.

---

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

---

This PR has been generated by Mend Renovate.

Greptile Summary

Bumps wretch from 3.0.8 to 3.0.9 across the pnpm workspace catalog and lock file. This is an automated Renovate patch update containing a bug fix for .fetchError swallowing user errors and a TypeScript type narrowing improvement for AbortAddon.controller().

• pnpm-workspace.yaml and pnpm-lock.yaml are updated consistently with the new version and integrity hash.
• Two pre-existing transitive dependencies (stream-to-promise@2.2.0, tsconfck@3.1.6) now show deprecated notices in the lock file — these were surfaced by pnpm's regeneration pass and are unrelated to wretch.

Confidence Score: 5/5

Straightforward patch dependency bump with no API surface changes and a bug fix; safe to merge.

The change is a single patch-level version bump for wretch, touching only the pnpm catalog and lock file. The upstream release fixes a bug where .fetchError incorrectly swallowed user-thrown errors, which is an improvement. No application code is modified.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Update dependency wretch to v3.0.9" | Re-trigger Greptile}

[qodo-code-review]

PR Summary by Qodo

Bump wretch to 3.0.9 (pnpm catalog + lockfile)

⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Bump wretch from 3.0.8 to 3.0.9 across the pnpm workspace catalog.
• Regenerate pnpm lockfile to reflect the updated wretch resolution.
• Capture new lockfile metadata (e.g., deprecation flags) from upstream packages.

Diagram

graph TD
  Dev["Renovate PR"] --> Cat["pnpm-workspace.yaml"] --> Pnpm["pnpm install"] --> Lock["pnpm-lock.yaml"] --> Wretch["wretch@3.0.9"]

  subgraph Legend
    direction LR
    _cfg["Config"] ~~~ _tool["Tooling"] ~~~ _dep["Dependency"]
  end

Loading

High-Level Assessment

The PR’s approach (update the workspace catalog pin and regenerate the lockfile) is the standard and lowest-risk way to roll forward a patch dependency update. Main follow-up is to run the usual CI checks (typecheck/tests) to validate any upstream behavior or typing changes.

Files changed (2) +10 / -8

Other (2) +10 / -8

pnpm-lock.yamlLock wretch to 3.0.9 and refresh lock metadata +9/-7

Lock wretch to 3.0.9 and refresh lock metadata

• Updates resolved wretch version from 3.0.8 to 3.0.9 in importers, packages, and snapshots. Lockfile regeneration also records new upstream metadata (e.g., added deprecation flags on some transitive entries).

pnpm-lock.yaml

pnpm-workspace.yamlBump workspace catalog wretch pin to 3.0.9 +1/-1

Bump workspace catalog wretch pin to 3.0.9

• Updates the shared pnpm catalog entry for wretch from 3.0.8 to 3.0.9 so workspace packages using the catalog resolve the new patch version.

pnpm-workspace.yaml

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review