chore: Use default protocol version in tests

[kabir]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @kabir, 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 streamlines how protocol versions are managed within the codebase, particularly in test environments. By linking a key specification version constant to a dynamic source and removing redundant explicit version settings in various handler tests, the changes promote a more robust and adaptable system. This ensures that tests automatically align with the current default protocol version, reducing the need for manual updates when the default changes.

Highlights

• Dynamic Protocol Version Constant: The SPEC_VERSION_1_0 constant in Utils.java has been updated to dynamically reference AgentCard.CURRENT_PROTOCOL_VERSION, ensuring it always reflects the current default protocol version.
• Test Suite Refactoring: Explicit protocolVersion("1.0") calls have been removed from AgentCard builder instances across gRPC, JSON-RPC, and REST handler tests. This change allows tests to rely on the default protocol version, improving maintainability and consistency.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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 refactors the codebase to rely on the default protocol version from AgentCard.CURRENT_PROTOCOL_VERSION instead of hardcoding "1.0", which is a good improvement for maintainability. The changes in the test files correctly remove the explicit version setting, simplifying the test setup. I have one suggestion regarding the naming of a constant in Utils.java to improve clarity and prevent potential confusion in the future.

[gemini-code-assist]

While it's a good practice to use AgentCard.CURRENT_PROTOCOL_VERSION to avoid hardcoding the version string, the constant name SPEC_VERSION_1_0 is now misleading. It implies the value is always "1.0", but it will change if AgentCard.CURRENT_PROTOCOL_VERSION is ever updated. This could lead to confusion for future maintainers.

To improve clarity and maintainability, please consider renaming this constant to reflect that it represents the current specification version, for example, CURRENT_SPEC_VERSION.

Suggested change

	public static final String SPEC_VERSION_1_0 = AgentCard.CURRENT_PROTOCOL_VERSION;
	public static final String CURRENT_SPEC_VERSION = AgentCard.CURRENT_PROTOCOL_VERSION;