Skip to content

Commit 49ea2fd

Browse files
committed
docs: update workers readme
1 parent 4f3bffa commit 49ea2fd

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

cloudflareworkers/README.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,4 +11,14 @@ $ wrangler -v
1111
Now, if you run `wrangler dev` within this directory, it should use the config
1212
in `wrangler.toml` to run the example.
1313

14-
You can also run `wrangler deploy` to deploy the example.
14+
You can also run `wrangler deploy` to deploy the example.
15+
16+
## ⚠️ Deprecation Notice
17+
18+
**This approach is currently deprecated and does not work as expected.**
19+
20+
After deploying to Cloudflare Workers, requests from CF edge nodes carry identifiable characteristics that cause many platforms (e.g., NodeSeek) to block or restrict access. Additionally, some platforms have disabled IPv6 access, and Cloudflare Workers cannot reliably force IPv4-only outbound connections.
21+
22+
The current workaround is to use Cloudflare Workers **only as a scheduled trigger** to invoke CircleCI webhooks, rather than performing check-ins directly.
23+
24+
If you're interested in making this approach work, contributions and further exploration are welcome!

0 commit comments

Comments
 (0)