run build before release

[UziTech]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @UziTech, 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 version bump within the package.json file, incrementing the package from "17.0.1-1" to "17.0.1-2". This change is intended to ensure that the build process is properly executed and reflected in the versioning before any new release is made.

Highlights

• Version Update: The package version in package.json has been incremented from "17.0.1-1" to "17.0.1-2". This change is likely part of a pre-release step to ensure the build process is executed before a new version is published.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/tests.yml

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 bumps the package version. My review identified one issue: the package-lock.json is out of sync with the version change in package.json, which can cause dependency inconsistencies. Please update it by running npm install.

Given the PR's title, I also suggest adding a prepare script to package.json (e.g., "prepare": "npm run build") to automatically run the build before publishing. This will ensure the distributed package always contains the latest compiled code.

[gemini-code-assist]

While the package version is updated here, the package-lock.json file appears to be out of sync. It still reflects version 17.0.1-0. To ensure dependency consistency and reproducible builds, please run npm install to update the lockfile and include it in this pull request.