fix(itk): exclude Go v0.3 from HTTP JSON scenarios#999
Open
KXHXK wants to merge 1 commit into
Open
Conversation
KXHXK
marked this pull request as ready for review
July 26, 2026 14:12
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.
Description
Summary
go_v03from all four nightlyHTTP_JSONinteroperability scenarios because A2A Go v0.3 does not expose REST/HTTP+JSON endpoints.0->4and4->0edges so each scenario's topology remains valid after the SDK list is shortened.Validation
Baseline scenario assertion failed on all four nightly HTTP_JSON scenarios before the change.
Post-change JSON and topology assertions passed: four HTTP_JSON scenarios exclude
go_v03, supported protocols retain it, and every edge index is valid..\docs\mvnw.cmd -q -pl itk -am -DskipTests packagepassed for the 42-module ITK dependency chain (run through an ASCII drive mapping to avoid the known Windowsprotocissue with non-ASCII workspace paths).git diff --checkpassed.Follow the
CONTRIBUTINGGuide.Make the Pull Request title follow the Conventional Commits specification.
Ensure the tests pass.
Appropriate READMEs were updated (not necessary for this scenario-only correction).
AI assistance: OpenAI Codex was used for repository analysis, the focused edit, and validation.
Fixes #979