🔄 daily merge: master → main 2025-11-27

[antfin-oss]

This Pull Request was created automatically to merge the latest changes from master into main branch.

📅 Created: 2025-11-27
🔀 Merge direction: master → main
🤖 Triggered by: Scheduled

Please review and merge if everything looks good.

[sourcery-ai]

The pull request #690 has too many files changed.

The GitHub API will only let us fetch up to 300 changed files, and this pull request has 6149.

[gemini-code-assist]

Summary of Changes

Hello @antfin-oss, 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 introduces a comprehensive overhaul of the Ray project's build and CI systems. It migrates the build system to Bazel, implements modern dependency management with uv and raydepsets, restructures the CI pipeline for better maintainability, enhances Docker image builds, and improves code formatting and linting. These changes collectively aim to improve the development experience, ensure code quality, and enhance the reliability and efficiency of the CI process.

Highlights

• Bazel Build System: Migrated the project to use Bazel for building and testing, enabling more efficient and reproducible builds.
• Dependency Management: Introduced uv and raydepsets for managing Python dependencies, ensuring consistent dependency versions across environments.
• CI Pipeline Restructuring: Refactored the CI pipeline into more modular and maintainable components, improving the overall efficiency and reliability of the testing process.
• Docker Image Builds: Enhanced Docker image builds by adding support for multiple architectures (x86_64, aarch64) and Python versions, and by optimizing image layering for faster build times.
• Code Formatting and Linting: Adopted pre-commit hooks and semgrep for code formatting and linting, ensuring code quality and consistency.
• Testing Improvements: Improved testing by adding new tests, refactoring existing tests, and enabling better test isolation and parallelization.

Ignored Files

• Ignored by pattern: .gemini/** (1)
  • .gemini/config.yaml
• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/stale_pull_request.yaml

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 is an automated daily merge from master to main, incorporating a large number of changes across the repository. The changes primarily focus on refactoring and improving the CI/CD pipeline, build system, and dependency management. Key improvements include modularizing Buildkite pipelines, migrating to uv and miniforge for Python dependency management, and refactoring Bazel build rules to use rules_pkg. There are also various code style improvements and modernizations in the C++ codebase. The changes are extensive and appear to be well-coordinated improvements to the project's infrastructure. I have one suggestion to improve encapsulation in a test utility class.

[gemini-code-assist]

For better encapsulation, the member variables of the Pip class should be private. The to_json and from_json functions can be declared as friends to allow them access to the private members. This prevents direct modification of the members from outside the class, making the code more robust and maintainable.

Suggested change

	class Pip {
	public:
	std::vector<std::string> packages;
	bool pip_check = false;
	std::vector<std::string> packages_;
	bool pip_check_ = false;
	Pip() = default;
	Pip(const std::vector<std::string> &packages, bool pip_check)
	: packages(packages), pip_check(pip_check) {}
	: packages_(packages), pip_check_(pip_check) {}
	class Pip {
	public:
	Pip() = default;
	Pip(const std::vector<std::string> &packages, bool pip_check)
	: packages_(packages), pip_check_(pip_check) {}
	friend void to_json(nlohmann::json &j, const Pip &pip);
	friend void from_json(const nlohmann::json &j, Pip &pip);
	private:
	std::vector<std::string> packages_;
	bool pip_check_ = false;
	};