Bump version to 0.0.1

[allenhutchison]

Bumps version to 0.0.1 in preparation for release.

[gemini-code-assist]

Summary of Changes

Hello @allenhutchison, 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 prepares the project for its initial release by standardizing version numbers across relevant package configuration files. It also includes minor updates to project metadata, such as descriptions, binary paths, keywords, author information, and licensing, to ensure consistency and accuracy for the upcoming release.

Highlights

• Version Bump: The project's version has been updated from "1.0.0" to "0.0.1" in both the root package.json and workspace-server/package.json.
• Metadata Updates: The package.json files have been updated with a refined description, adjusted binary path, and an expanded list of keywords. The workspace-server/package.json now explicitly lists the author and has updated its license to Apache-2.0.

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 prepares for the 0.0.1 release by updating version numbers and package metadata in the package.json files. The changes themselves are correct and improve consistency.

However, the scope of the update appears incomplete, leading to inconsistencies in the codebase. I've identified two critical issues in related files that were not part of this change but are directly affected by it:

1. Inconsistent Server Version: In workspace-server/src/index.ts on line 74, the McpServer is initialized with a hardcoded version "1.0.0". This should be updated to "0.0.1" to match the package version. To avoid this in the future, consider dynamically reading the version from package.json.
2. Broken Script Path: In scripts/auth-utils.js on line 7, the require path still points to ../workspace-mcp-server/dist/auth-utils.js. Based on the path change in the root package.json, this will break the script. The path should be updated to ../workspace-server/dist/auth-utils.js.

Addressing these points will ensure the release is consistent and functional.