Repository navigation
fix: deploy shared backend for chat and render changes - #1291
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Changes to registered Chat and Render Python backends were absent from the shared LangGraph deployment's push filters, so a merged backend correction could leave the existing deployment unchanged. Add both input paths and a registry-driven regression that checks the actual push filters against staged manifests and graph entrypoints.
The existing FREE deployment ID, pinned CLI, deployment command, generator behavior and AG-UI deployment workflow are unchanged.
Validation: the regression first reproduced 17 missing Chat/Render cases, then all 48 routing checks passed. The complete scripts suite passed 486 tests with 5 existing skips. Local generator cases required a 180-second command-line test timeout because this checkout contains Python virtual environments; the initial 60-second timeout failures were retained, and repository timeout settings were unchanged. Application sources, lockfiles and user files were verified unchanged.