From e02db4778893d744af9d91bd9b04cbad6d8f8c0e Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Tue, 8 Sep 2026 14:49:32 +0000
Subject: [PATCH] Version Packages

---
 .changeset/docs-alias-dependency-setup.md | 7 -------
 package/CHANGELOG.md                      | 8 ++++++++
 package/package.json                      | 2 +-
 3 files changed, 9 insertions(+), 8 deletions(-)
 delete mode 100644 .changeset/docs-alias-dependency-setup.md

diff --git a/.changeset/docs-alias-dependency-setup.md b/.changeset/docs-alias-dependency-setup.md
deleted file mode 100644
index 471e85a..0000000
--- a/.changeset/docs-alias-dependency-setup.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"expo-cloudflared": patch
----
-
-Setup is now a single `@expo/ngrok` alias dependency that works identically on npm, yarn (v1 and Berry), pnpm, and bun — replacing the four per-package-manager recipes.
-
-The old recipe (`dependencies: expo-cloudflared` + `overrides`/`resolutions: @expo/ngrok`) never created `node_modules/@expo/ngrok` in a normal Expo app: those fields only rewrite an *existing* dependency edge, and nothing depends on `@expo/ngrok` (Expo fetches it lazily at runtime). Expo therefore fell back to real ngrok. Declaring the alias as a direct dependency is what guarantees the path exists right after `install`. Also documents the monorepo case — the alias goes in the workspace you run `expo start` from — including the yarn-Berry gotcha that `resolutions` is honored only at the workspace root.
diff --git a/package/CHANGELOG.md b/package/CHANGELOG.md
index b948273..aaf68fe 100644
--- a/package/CHANGELOG.md
+++ b/package/CHANGELOG.md
@@ -1,5 +1,13 @@
 # expo-cloudflared
 
+## 4.2.2
+
+### Patch Changes
+
+- ccb003b: Setup is now a single `@expo/ngrok` alias dependency that works identically on npm, yarn (v1 and Berry), pnpm, and bun — replacing the four per-package-manager recipes.
+
+  The old recipe (`dependencies: expo-cloudflared` + `overrides`/`resolutions: @expo/ngrok`) never created `node_modules/@expo/ngrok` in a normal Expo app: those fields only rewrite an _existing_ dependency edge, and nothing depends on `@expo/ngrok` (Expo fetches it lazily at runtime). Expo therefore fell back to real ngrok. Declaring the alias as a direct dependency is what guarantees the path exists right after `install`. Also documents the monorepo case — the alias goes in the workspace you run `expo start` from — including the yarn-Berry gotcha that `resolutions` is honored only at the workspace root.
+
 ## 4.2.1
 
 ### Patch Changes
diff --git a/package/package.json b/package/package.json
index 0d8f7d8..02f528c 100644
--- a/package/package.json
+++ b/package/package.json
@@ -1,6 +1,6 @@
 {
   "name": "expo-cloudflared",
-  "version": "4.2.1",
+  "version": "4.2.2",
   "description": "Cloudflare Tunnel for Expo — a drop-in replacement for `@expo/ngrok`. Powers `expo start --tunnel` using Cloudflare Tunnel instead of ngrok.",
   "source": "src/index.ts",
   "main": "dist/index.js",