chore: bump version to 0.0.3 - #54
Conversation
Summary of ChangesHello @allenhutchison, I'm Gemini Code Assist1! 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 synchronizes the project's version number to 0.0.3, correcting an oversight from a previous tagging operation. The changes ensure that all package manifests and the server's internal version declaration reflect the intended release number, maintaining consistency across the codebase. Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request bumps the version of the package and its workspace to 0.0.3. The changes in package.json, package-lock.json, and workspace-server/package.json are correct and reflect the version bump.
I've added one suggestion in workspace-server/src/index.ts to dynamically read the version from package.json instead of hardcoding it. This would improve maintainability and simplify your versioning scripts, making the process less error-prone in the future.
| const server = new McpServer({ | ||
| name: "google-workspace-server", | ||
| version: "0.0.1", | ||
| version: "0.0.3", | ||
| }); |
There was a problem hiding this comment.
To improve maintainability and avoid having to update the version number in multiple places, consider reading the version dynamically from package.json. This would make your versioning process more robust and less error-prone.
With this change, you would only need to update the package.json file, and you could simplify your set-version.js script and the version script in your root package.json.
| const server = new McpServer({ | |
| name: "google-workspace-server", | |
| version: "0.0.1", | |
| version: "0.0.3", | |
| }); | |
| const { version } = require('../package.json'); | |
| const server = new McpServer({ | |
| name: "google-workspace-server", | |
| version, | |
| }); |
Updates version numbers to 0.0.3 in package.json files and index.ts. This was missed in the previous tag.