chore: bump version to 0.14.0

[adelin-b]

Summary

• Bumps version in package.json, apps/ui/package.json, and apps/server/package.json from 0.13.0 to 0.14.0
• The v0.14.0 release was tagged without updating these version strings

Test plan

• Verify automaker --version reports 0.14.0 after install

Summary by CodeRabbit

• Chores
  • Version updated to 0.14.0 across all packages

[gemini-code-assist]

Summary of Changes

Hello @adelin-b, 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 addresses a versioning discrepancy by updating the version field in the main, UI, and server package.json files to 0.14.0. The primary goal is to align the codebase's declared version with the recently released v0.14.0 tag, ensuring consistency and accurate version reporting across the Automaker project.

Highlights

• Version Bump: The project's version has been updated from 0.13.0 to 0.14.0 across all relevant package.json files.
• Release Synchronization: This change synchronizes the version strings with the v0.14.0 release tag, which was previously created without these updates.

🧠 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.

Changelog

• apps/server/package.json
  • Updated the package version from "0.13.0" to "0.14.0".
• apps/ui/package.json
  • Updated the package version from "0.13.0" to "0.14.0".
• package.json
  • Updated the root package version from "0.13.0" to "0.14.0".

Activity

• The pull request was opened by adelin-b to bump the project version.
• A test plan was provided to verify automaker --version reports 0.14.0 after installation.

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. ↩

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Version number bumped from 0.13.0 to 0.14.0 across the root and both server and UI package.json files. No functional changes, dependencies modified, or control flow alterations.

Changes

Cohort / File(s)	Summary
Version Update package.json, apps/server/package.json, apps/ui/package.json	Version field updated from 0.13.0 to 0.14.0 in all package manifest files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop, a skip, a version bop,
From 0.13 we gladly pop,
To 0.14 we now ascend,
Three little bumps from end to end,
No logic bent, no code rearranged,
Just numbers changed! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'chore: bump version to 0.14.0' accurately and concisely describes the main change—updating version numbers across package.json files from 0.13.0 to 0.14.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This PR correctly bumps the version to 0.14.0 in all relevant package.json files, aligning them with the recent release tag. I've added a comment regarding an opportunity to improve the release automation to prevent the need for such manual changes in the future.

[gemini-code-assist]

This version bump is correct. However, the need for a manual update across three separate package.json files indicates a potential improvement in your release process. The existing apps/ui/scripts/bump-version.mjs script handles versioning for the ui and server apps but omits this root package.json. I recommend extending that script to also update the version here. This would fully automate the version bumping process, reduce manual effort, and prevent inconsistencies in future releases.

[gsxdsm]

@webdevcody fyi - need your approval on main

[gsxdsm]

I bumped to v15