fix(deploy): target sonicjs-client-directory Pages project for client.sonicjs.com

Merged
LA
9h ago
+1-1

Root cause

client.sonicjs.com is served by the sonicjs-client-directory Cloudflare Pages project (confirmed via wrangler pages project list), not sonicjs-sdk-demo. The workflow has been deploying to the wrong project, leaving the live site on a 1-year-old build.

Fix

Change --project-name sonicjs-sdk-demo → --project-name sonicjs-client-directory in deploy-demo.yml.


Summary by cubic

Fixes the deployment workflow so client.sonicjs.com receives current builds. The workflow was deploying to the sonicjs-sdk-demo Cloudflare Pages project, but the site is served by sonicjs-client-directory, leaving the live site on a stale 1-year-old build. The deploy command now targets sonicjs-client-directory.

RetriggerView in GreptileConfidence Score: 4/5

The workflow change appears safe to merge, with a non-blocking follow-up to align the manual deploy command.

Findings

  1. P2 Manual deploys still target elsewhere ▶

Summary

Changes the demo workflow to deploy to sonicjs-client-directory, the Pages project identified in the PR as serving client.sonicjs.com.

  • The demo workflow sends its Pages upload to the project serving client.sonicjs.com.

Reviews (1) · Last reviewed commit: "fix(deploy): target sonicjs-client-direc..." · Reviewed by Greptile