Skip to content

revert(cli): keep HeyGen API traffic on stable prod - #3202

Merged
miguel-heygen merged 2 commits into
mainfrom
revert/ef-canary-route
Aug 11, 2026
Merged

revert(cli): keep HeyGen API traffic on stable prod#3202
miguel-heygen merged 2 commits into
mainfrom
revert/ef-canary-route

Conversation

@miguel-heygen

Copy link
Copy Markdown
Collaborator

Summary

Normal HyperFrames CLI traffic now stays on stable EF prod. This reverts hyperframes#3201 and removes the older canary route injection from publish and feedback, so login, token lifecycle, API-key billing calls, cloud operations, publish, and feedback no longer depend on a pre-release backend deployment.

The repository now contains zero heygen_route injections. The unrelated telemetry/PostHog canary rollout system is unchanged.

Test plan

  • TDD: 3 expected failures before removing the pre-existing publish/feedback headers
  • bun run --cwd packages/cli test — 2,581 passed, 3 skipped
  • bun run --cwd packages/cli typecheck
  • changed-file oxlint and oxfmt checks
  • bun run build
  • repo-wide heygen_route audit — zero matches

Compound Engineering
GPT-5

@somanshreddy somanshreddy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified at d00271ce — both asks pass. ✅

Zero EF route injection. Grepped all four source files at head: heygen_route count = 0 in publishProject.ts, submitFeedback.ts, client.ts, and oauth.ts; heygenRoute.ts is deleted (404 at head); every withHeygenCanaryRoute(...) call is reverted to a plain header object and all imports of the helper are gone. So auth/token/refresh/revoke/code-exchange, API-key + OAuth via buildAuthHeaders (which also covers cloud + /v3/users/me), publish (all 3 callsites), and feedback all route to prod now — including the older pre-#3201 canary headers on publish/feedback.

No telemetry-canary overreach. Changed-files list is exactly the 10 EF-route files; none of the PostHog/rollout canary surface (core/src/canary.ts, canaryRegistry.ts, cli|studio/telemetry/canary.ts, check-canary-sunset.ts, de-canary-suite.sh, validate-release-channel.mjs) is touched. The two "canary" concepts stayed cleanly separated.

Nit (non-blocking, intentional): publishProject.e2e.test.ts's fetchPublicProject now calls fetch(url,) with a trailing comma after the headers arg was dropped — valid JS, format-clean.

Reads as a complete, correct reversal. LGTM on the verification; leaving the stamp to an authorized approver.

@miguel-heygen
miguel-heygen merged commit 08934bf into main Aug 11, 2026
43 of 44 checks passed
@miguel-heygen
miguel-heygen deleted the revert/ef-canary-route branch August 11, 2026 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants