Release v0.4.0

[pan-x-c]

Description

As the title says

Checklist

Please check the following items before code is ready to be reviewed.

• Code has passed all tests
• Docstrings have been added/updated in Google Style
• Documentation has been updated
• Code is ready for review

[gemini-code-assist]

Summary of Changes

Hello @pan-x-c, 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 announces the official release of Trinity-RFT v0.4.0, with a primary focus on integrating the Tinker backend. This new backend allows users to perform model training without requiring GPUs, significantly broadening the accessibility of the framework. The changes include updating release notes in the READMEs, adding detailed documentation for the Tinker backend in both English and Chinese, and refining dependency installations within the Docker build processes.

Highlights

• Trinity-RFT v0.4.0 Release: Officially released version 0.4.0, introducing significant new features and benchmarks for the Trinity-RFT framework.
• Tinker Backend Integration: Added support for the Tinker backend, enabling model training on CPU-only devices, which broadens the accessibility of the framework.
• Comprehensive Documentation: New English and Chinese tutorials (example_tinker_backend.md and example_tinker_backend_zh.md) have been added, detailing the setup, configuration, usage, and limitations of the Tinker backend.
• Dependency Management Refinement: Adjusted pyproject.toml and Dockerfiles to ensure correct and robust installation of transformer_engine for Megatron.

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

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 prepares for the v0.4.0 release. The changes include updating README files with release news, adding new documentation for the Tinker backend, and adjusting dependency installation for transformer_engine to resolve build issues. The new documentation for the Tinker backend is well-detailed. My review identifies and suggests fixes for broken links within this new documentation to ensure users can access the example configuration files.