feat: add version syncing scripts and hooks

[allenhutchison]

This PR introduces a mechanism to keep version strings in sync across the codebase using the npm version lifecycle hook.

Changes

• Added scripts/set-version.js to update versions in:
  • package.json
  • workspace-server/package.json
  • workspace-server/src/index.ts
• Updated package.json to include set-version and version scripts.
• Updated scripts/release.js to fallback to package.json version if GITHUB_REF_NAME is missing.

How to Test

1. Run npm run set-version 0.0.2 and verify all files are updated.
2. Run npm version patch and verify it creates a commit with all files updated.
3. Run npm run release and verify the output json has the correct version.

Fixes #27

[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 implements a comprehensive solution for synchronizing version numbers across various project files. By introducing a dedicated script and integrating it with the npm version lifecycle, the changes aim to automate version management, reduce the potential for discrepancies, and streamline the release process for the project.

Highlights

• Automated Version Syncing: A new script, scripts/set-version.js, has been introduced to automatically update version strings across package.json files (root and workspace-server) and within workspace-server/src/index.ts.
• NPM Version Lifecycle Integration: The root package.json now includes set-version and version scripts, allowing the new syncing mechanism to be triggered manually or automatically via npm version lifecycle hooks.
• Release Script Robustness: The scripts/release.js file has been updated to gracefully fall back to using the version from the root package.json if the GITHUB_REF_NAME environment variable is not available, ensuring consistent versioning during releases.

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 introduces a useful mechanism for synchronizing version numbers across multiple files using npm's version lifecycle hook. The implementation is straightforward and the logic is sound. The update to the release.js script to use the package.json version as a fallback is also a good improvement.

I've added a couple of suggestions for the new scripts/set-version.js file to improve its robustness with better error handling and to make a minor performance optimization. Overall, this is a solid addition to the project's tooling.