Release v0.8.7-rc.2 - forge-core sync with rmcp 0.10.0

[namastex888]

Summary

• Synced versions between automagik-forge and forge-core to 0.8.7-rc.2
• forge-core now has rmcp = "0.10.0" (was 0.8.5)
• All git tag refs point to v0.8.7-rc.2

Changes

• Version bump to 0.8.7-rc.2 across all package.json and Cargo.toml
• forge-core git tag refs updated to v0.8.7-rc.2
• forge-core patched with rmcp 0.10.0, axum features, zerocopy patch

Test plan

• PR merge triggers release.yml workflow
• Builds should succeed on all platforms (linux-x64, linux-arm64, macos-arm64, windows-x64)
• npm publish to next tag

[gemini-code-assist]

Summary of Changes

Hello @namastex888, 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 focuses on preparing for the v0.8.7-rc.2 release candidate by performing a comprehensive version synchronization across the automagik-forge and forge-core ecosystems. It ensures that all internal packages and their external git tag references are aligned with the new release candidate, alongside an important update to the rmcp dependency and the application of specific patches to forge-core for enhanced functionality and stability.

Highlights

• Version Synchronization: All automagik-forge and forge-core components have been synchronized to version 0.8.7-rc.2.
• Dependency Update: forge-core now utilizes rmcp version 0.10.0, upgraded from 0.8.5.
• Git Tag Alignment: All git tag references for forge-core components have been updated to point to v0.8.7-rc.2.
• Core Patches: forge-core has received patches including axum features and a zerocopy update.

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 package versions to 0.8.7-rc.2 and syncs the forge-core dependency to tag v0.8.7-rc.2. The changes are consistent with preparing for a new release. I've identified a version inconsistency with the forge-core dependency where the crate versions in Cargo.lock do not match the new git tag. I've also included a suggestion to enhance the maintainability of your git dependencies for the long term.

[gemini-code-assist]

There's a version mismatch here. The package version is 0.8.7-rc.1, but the git tag in the source URL is v0.8.7-rc.2. This suggests that the crate versions within the forge-core repository were not bumped to match the new tag. For release consistency, the crate versions should match the git tag version. This seems to be the case for all forge-core dependencies in this file (e.g., deployment, executors, etc.). Please ensure versions are synchronized in the forge-core repository for tag v0.8.7-rc.2.

[gemini-code-assist]

These repeated git dependency declarations with tags can be hard to maintain. While the bump-forge-core.sh script helps, you might consider using a git submodule for forge-core.

With a submodule, you could replace these git dependencies with path dependencies, like this:

# In forge-app/Cargo.toml
db = { path = "../path/to/forge-core/db" }
services = { path = "../path/to/forge-core/services" }
# ... and so on

This would tie the dependency version to a single commit hash of the submodule, making it easier to manage and update all forge-core crates at once by just updating the submodule pointer. This would also simplify your release automation scripts.