ci(guide): run browser tests explicitly [Codex] - #1345
Conversation
Expose the Playwright container browser cache and split guide Vitest into its own CI step.
Guide Cloudflare deployment⛅️ wrangler 4.114.0 To deploy this version to production traffic use the command wrangler versions deploy Changes to non-versioned settings (config properties 'logpush' or 'tail_consumers') take effect after your next deployment using the command wrangler versions deploy Changes to triggers (routes, custom domains, cron schedules, etc) must be applied with the command wrangler triggers deploy |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
guide | 8247c52 | Commit Preview URL Branch Preview URL |
Sep 13 2026, 02:34 PM |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Cloudflare deploymentDeployement ID: 3117cf34-ca19-435d-bad6-85fb4984e0bd ⛅️ wrangler 4.114.0 ✨ Uploading _redirects |
The guide's Browser Mode suite was configured but not run by the pull-request workflow, and its pinned Chromium cache was not exposed inside the Playwright container.
This configures the existing Playwright container cache and gives the guide suite its own named CI step alongside the docs suite. Browser-test failures will now be visible independently in pull requests.