Skip to content

chore: bump version to 0.0.3 - #54

Merged
allenhutchison merged 1 commit into
mainfrom
adh/chore/bump-version-0.0.3
Dec 3, 2025
Merged

chore: bump version to 0.0.3#54
allenhutchison merged 1 commit into
mainfrom
adh/chore/bump-version-0.0.3

Conversation

@allenhutchison

Copy link
Copy Markdown
Contributor

Updates version numbers to 0.0.3 in package.json files and index.ts. This was missed in the previous tag.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @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

  • Version Bump: The project's version has been updated from 0.0.1 to 0.0.3 across all relevant package configuration files and the main server initialization.
  • Dependency Configuration: The peer: true property has been removed from several dependency entries within package-lock.json.
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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment on lines 72 to 75
const server = new McpServer({
name: "google-workspace-server",
version: "0.0.1",
version: "0.0.3",
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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.

Suggested change
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,
});

@allenhutchison
allenhutchison merged commit dd0ba4c into main Dec 3, 2025
6 checks passed
@allenhutchison
allenhutchison deleted the adh/chore/bump-version-0.0.3 branch December 3, 2025 23:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants