Fix production WebSocket URL for web-cli#149
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughUpdated the default production WebSocket URL from "wss://web-cli.ably.com" to "wss://web-cli-terminal.ably.com" in the web CLI application. The WebSocket URL resolution logic remains unchanged. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
f8a9a6c to
b96dfb0
Compare
b96dfb0 to
6471174
Compare
Updated to the new production endpoint.
Note
Low Risk
Low-risk config change: updates the default production WebSocket URL used by the
examples/web-cliapp and expands CI triggers to includeexamples/**. Main risk is misconfiguration causing the example web client to connect to the wrong production endpoint.Overview
Updates the
examples/web-clidefault production WebSocket URL to use the newwss://web-cli-terminal.ably.comendpoint.Adjusts the
Run TestsGitHub Actions workflow path filters so pushes/PRs that changeexamples/**also trigger the test job.Written by Cursor Bugbot for commit 6471174. This will update automatically on new commits. Configure here.
Summary by CodeRabbit