Merge main to epic/1.0

[bartek-gralewicz]

Description

Merging recent changes from main into an epic/1.0 branch to avoid difficult conflicts in the future.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates recent changes from the main branch into the epic/1.0 branch, primarily to proactively manage and avoid potential merge conflicts. The updates encompass a broad range of dependency upgrades, a crucial enhancement to AgentCard parsing for improved compatibility with different data models, and a significant refactoring of the REST transport layer for cleaner and more efficient request handling. The CLI tool also received a minor but useful update for transport selection.

Highlights

• Dependency Updates: Numerous project dependencies, including @a2a-js/sdk, minimatch, rollup and its various platform-specific packages, flatted, simple-git, fast-xml-parser, strnum, and brace-expansion, have been updated to their latest versions. Additionally, fast-xml-builder and path-expression-matcher were introduced in the sample project's package-lock.json.
• AgentCard Normalization: The AgentCardResolver now includes robust logic to automatically detect and normalize AgentCard structures, effectively bridging the gap between JSON Schema and Protobuf JSON representations for security schemes and entries. This ensures consistent internal handling regardless of the incoming format.
• REST Transport Handler Refactoring: The REST transport handler has been significantly simplified by removing internal snake_case to camelCase normalization and input validation methods. Instead, it now leverages FromProto conversions for incoming requests and integrates validation directly into its public methods, streamlining the request processing pipeline.
• CLI Tool Transport Selection: The command-line interface (CLI) tool has been enhanced to support specifying a preferred transport mechanism via a new --transport= command-line argument, offering greater flexibility in how the client interacts with agents.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/coverage-comment.yml
  • .github/workflows/unit-tests.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request merges changes from the main branch, including dependency updates, changelog entries, and significant refactorings. The client-side AgentCardResolver has been improved to handle both JSON Schema and Protobuf-based formats for agent cards, increasing interoperability. On the server side, the REST transport handler has been refactored to use Protobuf types for request parsing, which simplifies the codebase by removing manual data normalization. My review includes one suggestion to further improve the robustness of the agent card parsing logic.

[gemini-code-assist]

The type assertion card as AgentCard assumes that if the card is not in Protobuf format, it must be in the correct JSON Schema format. This could lead to runtime errors if the received card is malformed but doesn't trigger the isProtoAgentCard heuristic. To improve robustness, consider adding a basic validation check for the non-Protobuf format, for example by checking for the presence of a required field like protocolVersion.

Suggested change

	return card as AgentCard;
	if (card && typeof card === 'object' && 'protocolVersion' in card) {
	return card as AgentCard;
	}
	throw new Error('Received malformed AgentCard');