Upgrade Growth to Dawn 0.8.26 and native Vercel output - #1046
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
blove
enabled auto-merge (squash)
September 7, 2026 02:39
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade lifecycle and company research to Dawn 0.8.26. Lifecycle now deploys Dawn's native Node 24 Vercel Build Output API artifact, with a thin wrapper preserving exact service-token authentication, the separate Dawn database binding, health deployment identification, and the 60-second limit. This removes generated-source rewrites and the old source-function entry. Company research remains on LangSmith.
The workspace lock preserves app-local SDK/Zod 4 peer resolution and raises the shared LangChain core minimum required by the upgraded providers. Resend's optional renderer is included to keep the Vercel artifact self-contained. Existing enrichment budgets, schema workaround, and business-morning email schedule remain in place.
Validation: clean npm ci; lifecycle and research tests, type checks, lint, and builds; Growth and dependent library tests; isolated native function import and authorization checks; authenticated create/read/delete persistence across two fresh Node 24 processes using a disposable Neon database while the Growth database URL was deliberately unreachable. The disposable database was removed.