fix(publish-runtime): re-add 5 templates wrongly removed from cascade — fixes #2566 - #2575
Merged
HongmingWang-Rabbit merged 2 commits intoMay 3, 2026
Merged
Conversation
…#2566) The PR #2536 cascade prune ('deprecated, no shipping images') was empirically wrong. Re-confirmed 2026-05-03: - continuous-synth-e2e.yml defaults to langgraph as its primary canary - All 5 'deprecated' templates have successful publish-image runs in the past 24h: langgraph, crewai, autogen, deepagents, gemini-cli Symptom this fixes — issue #2566 (priority-high, failing 36+h): Synthetic E2E (staging): langgraph adapter A2A failure 'Received Message object in task mode' — failing for >36h Today at 11:06 commit e1628c4 fixed the underlying a2a-sdk strict-mode issue in workspace/a2a_executor.py. publish-runtime fired at 11:13 and cascaded — but only to claude-code, hermes, openclaw, codex. langgraph was excluded by the prune, so its image stayed on the broken runtime and the synth E2E (which defaults to langgraph) kept failing despite the fix being live in PyPI. After this lands + the next runtime publish fires, langgraph image re-bakes with the fix and synth-E2E goes green. Test plan: - [x] yaml-validate the workflow - [ ] After merge, watch publish-runtime cascade to all 9 templates - [ ] Confirm langgraph publish-image fires + succeeds - [ ] Confirm next continuous-synth-e2e run goes green Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
HongmingWang-Rabbit
requested a review
from hongmingwang-moleculeai
as a code owner
May 3, 2026 12:42
The cascade-list-vs-manifest drift gate (PR #2556's behavior-based test) caught my previous-commit cascade additions as 'extra-in-cascade'. Manifest is the source of truth — restoring there. All 5 templates have successful publish-image runs in the past 24h (verified before the cascade fix), and continuous-synth-e2e defaults to langgraph as its primary canary. None deprecated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Re-add
langgraph,crewai,autogen,deepagents,gemini-clito thepublish-runtime.ymlcascadeTEMPLATESlist. They were removed by #2536 with the rationale "deprecated, no shipping images" — empirically wrong.Why this fixes #2566
continuous-synth-e2e.ymldefaults to langgraph as its primary canary (line 44, "fastest, default"). When today's a2a-sdk strict-mode fix landed (commite1628c4at 11:06),publish-runtimefired at 11:13 and cascaded — but only toclaude-code, hermes, openclaw, codex. langgraph was excluded, so its image stayed on the broken runtime.So #2566 was actually a cascade-scope drift bug masquerading as an a2a regression. The a2a fix is correct and deployed in PyPI 0.1.94; it just never made it into the langgraph image.
Verified all 5 are still alive
Per
gh run list --workflow publish-image --limit 1per repo, every "deprecated" template had successful publish-image runs within the past 24h. None are dormant.Followup (out of scope here)
The original comment proposed: "Long-term: derive this list from manifest.json so the cascade can't drift again — tracked in RFC #388 as a Phase-1 invariant." Still the right move — this PR re-adds the data manually, but the structural fix lives in RFC #388.
Test plan
🤖 Generated with Claude Code