chore: Use 1.0.0.Alpha1-SNAPSHOT and fix update-version.sh

[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 primarily focuses on a significant version update for the a2a-java-sdk project, moving from "0.4.0.Alpha1-SNAPSHOT" to "1.0.0.Alpha1-SNAPSHOT" across all relevant Maven pom.xml files and an example JBang script. Additionally, it includes a minor but important fix to the update-version.sh script to improve its robustness when handling optional arguments.

Highlights

• Version Update: The project's parent version has been updated across all Maven pom.xml files and a JBang example script from "0.4.0.Alpha1-SNAPSHOT" to "1.0.0.Alpha1-SNAPSHOT".
• Shell Script Robustness: The update-version.sh script was fixed to correctly handle unset optional arguments, improving its reliability.

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 primarily updates the project version from 0.4.0.Alpha1-SNAPSHOT to 1.0.0.Alpha1-SNAPSHOT across numerous pom.xml files and a JBang script. It also includes a fix in update-version.sh to correctly handle optional arguments when set -u is active. The changes are largely correct, but I've identified a small improvement for the shell script to align with best practices for error handling.

[gemini-code-assist]

It is a standard best practice in shell scripting to redirect error messages to standard error (stderr) instead of standard output (stdout). This ensures that error messages do not get mixed with the script's normal output, which is important for logging and when piping the script's output to other commands. You should consider applying this change to other error messages in this script as well.

Suggested change

	echo "❌ Error: Invalid third argument. Only '--dry-run' is supported."
	echo "Usage: $0 FROM_VERSION TO_VERSION [--dry-run]"
	echo "❌ Error: Invalid third argument. Only '--dry-run' is supported." >&2
	echo "Usage: $0 FROM_VERSION TO_VERSION [--dry-run]" >&2