fix(cloud): align Worker core stub to main — prevent 0-export promote break - #11902
Conversation
… break After the #11861 promote, the runWithTrajectoryPurpose Worker stub was deduped DIFFERENTLY on each branch: #11865 removed the second copy on main (kept the top 'pass-through' one); #11857 removed the top copy on develop (kept the other). A develop->main 3-way merge would then apply BOTH removals and drop runWithTrajectoryPurpose entirely (verified: merge-tree yields 0 exports) — silently re-breaking the Worker build on the next promote. Fix: make develop's stub byte-identical to main's (single 'pass-through' export, matching what's already deployed on prod). Future promotes are now a no-op on this file. Functionally identical no-op stub either way.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization 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:
✨ 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 |
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
1 participant
After #11861 promote,
runWithTrajectoryPurposein the Worker stub was deduped differently per branch — #11865 (main) kept the top copy, #11857 (develop) kept the other. A develop→main merge applies both removals → 0 exports → Worker build breaks on the next promote (verified viagit merge-tree). Aligns develop's stub byte-identical to main's (the version already on prod). Future promotes are a no-op on this file. —[cloud-frontdoor]