fix: read version from package.json, add CI workflow

[GreyC]

Summary

• Read CLI version dynamically from package.json instead of hardcoding 0.1.0
• Add resolveJsonModule: true to tsconfig.json to support the JSON import
• Add GitHub Actions CI workflow to build on PRs targeting main

Test plan

• jules_cli --version returns the version from package.json
• CI workflow triggers on PR and runs npm install + npm run build

generated by CC

[gemini-code-assist]

Summary of Changes

Hello, 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 enhances the jules_cli project by improving its version management and development workflow. It transitions the CLI to dynamically retrieve its version from package.json, ensuring consistency and reducing manual updates. Additionally, it integrates a new GitHub Actions CI workflow to automate build processes for pull requests, thereby streamlining development and ensuring code quality.

Highlights

• Dynamic CLI Versioning: The CLI now reads its version directly from package.json, eliminating hardcoded values.
• TypeScript Configuration Update: tsconfig.json was updated to enable JSON module imports, supporting the dynamic versioning.
• CI Workflow Integration: A GitHub Actions workflow was added to automate builds on pull requests targeting the main branch.

Changelog

• packages/cli/package-lock.json
  • Added a new package-lock.json file, likely reflecting updated or newly installed dependencies.
• packages/cli/src/index.ts
  • Modified to import the version field from ../package.json.
  • Updated the program.version() call to use the imported version instead of a hardcoded string.
• packages/cli/tsconfig.json
  • Added the "resolveJsonModule": true compiler option to enable importing JSON files as modules.

Ignored Files

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

Activity

• The pull request description includes a test plan for verifying the dynamic versioning and CI workflow.
• The PR was generated by a tool or process indicated as "CC".

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 updates the CLI to read its version from package.json instead of a hardcoded value, which is a good practice. The change is supported by an update to tsconfig.json to allow JSON module imports. I have one suggestion regarding code style to improve maintainability.