chore(showcase): bump @ag-ui/langgraph to 0.0.33 in langgraph-typescript overrides#5016
Merged
Merged
Conversation
…h-typescript R3b bumped the monorepo packages but missed two showcase-level override pins. The langgraph-typescript integration pins @ag-ui/langgraph directly in both its top-level and src/agent package.json files, bypassing whatever @copilotkit/runtime transitively resolves. Without this bump, the showcase LGT Docker image bakes 0.0.32 even though the monorepo runtime/sdk-js are on 0.0.33 (R3b). This is what's keeping the D6 LGT probe RED. Path filter showcase/** matches, so showcase_build.yml fires on merge to rebuild + Railway-redeploy langgraph-typescript with the real 0.0.33.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📣 Social Copy GeneratorGenerate social media copies (Twitter/X, LinkedIn, Blog Post) for this PR using Claude.
|
pull Bot
pushed a commit
to TheTechOddBug/CopilotKit
that referenced
this pull request
May 26, 2026
Extends the active rendering path with D6 support so dashboard cells
can display D6 ("parity vs reference") state. cell-model.ts gains
ceilingDepth | 6 + d6 TestLevel field + resolveD6() + D6-ceiling
chip-color algorithm. unified-cell.tsx + feature-grid.tsx render the
new D6 chip. live-status.ts gets the small Dimension/BadgeRender delta
the branch needed.
Until d6:<slug>/<featureId> PB rows start flowing (separate PR for the
D6 probe driver + per-framework fixtures), every cell renders D6 gray
("no data -- probe pending"). This is the accurate state -- visibility
without functional risk.
Cherry-picked from feat-d6-everything-works (the per-framework fixtures
branch). The remainder of that branch -- d6-all-pills driver, fixture
reorg, harness config -- lands in a follow-up PR now that the ag-ui
header-forwarding prerequisites (CopilotKit#4984, CopilotKit#4951, CopilotKit#5015, CopilotKit#5016) are in.
jpr5
added a commit
that referenced
this pull request
May 26, 2026
… + harness scoping (#5022) ## Summary Lands the per-framework fixture reorg + D6 probe driver + harness scoping work that was parked behind the ag-ui header-forwarding chain (now shipped via #4984, #4951, #5015, #5016). This is the foundational data layer the D6 dashboard needs to populate. Slice 1 (#5018) shipped the rendering plumbing earlier today; this PR makes d6:<slug>/<featureId> PB rows start flowing. ## What ships - 477 per-integration aimock fixtures organized under `d4/`, `d6/`, `shared/` directories (flat `d5-all.json` / `feature-parity.json` deprecated) - Every fixture keyed by `match.context` to enforce per-integration isolation (server-side routing already merged in aimock #226) - D6 all-pills probe driver + per-integration scoping in showcase-harness - X-AIMock-Context header propagation in 18 integration Playwright configs - D6-ceiling chip color algorithm (D6 is integration-scoped aggregate, maxPossible raised from 5 to 6) - Docker-compose updates for the new fixture dir layout - 12 HITL fixtures migrated from main's d5-all.json additions into shared/_migrated-from-d5-all-hitl.json ## Why this is safe to ship now - ag-ui/LangGraph configurable+context HTTP 400 blocker is fixed (#5015 + #5016) - sdk-python 0.1.91 with `_extract_forwarded_headers_from_config` is on PyPI and pinned across showcase - aimock server-side context routing is already live (aimock #226) - The SDK overlay hacks the branch carried locally are now redundant — discarded before rebase ## Pre-existing CI note `@copilotkit/web-inspector:test` has a pre-existing failure (`window.localStorage.clear is not a function` in telemetry tests) — verified on clean main checkout. Not introduced by this PR. ## Follow-ups - Distribute migrated HITL fixtures from shared/_migrated-from-*.json into per-integration d6/<slug>/ files - Slice 2: D6 drilldown DIMENSIONS + AdaptiveStatsBar rollup section - LGP gen-ui-interrupt second-pill framework bug (Hypothesis B in useInterrupt hook)
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
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.
Summary
Bumps two showcase-level
@ag-ui/langgraphoverride pins from0.0.32to0.0.33:showcase/integrations/langgraph-typescript/package.jsonshowcase/integrations/langgraph-typescript/src/agent/package.jsonRegenerates both
package-lock.jsonfiles.Why this is needed (after R3b already shipped)
R3b (#5015) bumped
packages/runtimeandpackages/sdk-jsto consume@ag-ui/langgraph@0.0.33. But the langgraph-typescript showcase integration pins@ag-ui/langgraphdirectly in its ownpackage.jsonfiles viaoverrides, which overrides whatever the runtime transitively pulls. Without this PR, the LGT Docker image bakes 0.0.32 and the D6 LGT probe stays RED.This is the final ag-ui-side bump needed to complete the LGT header-forwarding chain end-to-end.
What's in @ag-ui/langgraph 0.0.33
(Same as documented in #5015.) Per-request
onRequesthook, prepareStream configurable+context partition fix for langgraph-api 0.7+, mergeConfigs context_schema allowlist.Test plan
showcase_build.ymlauto-fires (path filtershowcase/**matches)