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

[antfin-oss]

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

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

Please review and merge if everything looks good.

[sourcery-ai]

The pull request #672 has too many files changed.

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

[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 set of changes aimed at modernizing the build and test infrastructure, improving dependency management, and enhancing code quality. The changes span multiple areas, including Bazel configurations, Buildkite pipelines, Dockerfiles, and linting scripts, resulting in a more streamlined, reliable, and maintainable development process.

Highlights

• Bazel Configuration Updates: Modified .bazelrc to enable strict action environment, set compiler options for various platforms, and ignore warnings for third-party code. Also updated test configurations for CI.
• Buildkite Pipeline Changes: Restructured .buildkite configurations by adding _images.rayci.yml and modifying existing YAML files to streamline the build process and introduce new image building steps.
• Dependency Management: Introduced dependencies.rayci.yml to manage pip-compile dependencies and raydepsets, ensuring consistent dependency versions across the project.
• Core Test Updates: Modified core.rayci.yml to refine core tests, including adjustments to test tags, dependencies, and build configurations.
• Data Test Modifications: Updated data.rayci.yml to align with new build configurations and test setups, focusing on arrow versions and test parallelization.
• LLM Test Configuration: Adjusted llm.rayci.yml to specify the correct base images and CUDA versions for LLM tests.
• macOS Build Adjustments: Refactored macos.rayci.yml to streamline macOS builds, including changes to instance types and build scripts.
• Release Automation Enhancements: Enhanced release automation scripts and configurations, including updates to Dockerfiles and pre-release checks.
• Code Formatting and Linting: Updated linting configurations, including .pre-commit-config.yaml and related scripts, to enforce code style and quality.
• Core C++ Changes: Refactored Core C++ code to remove some dependencies and update the gRPC implementation.

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 a large automated merge from master to main, containing a significant number of changes. The primary focus of these changes is a major refactoring of the CI/CD pipelines and the Bazel build system. Key changes include modularizing Buildkite steps, expanding test matrices for better coverage, and updating dependency management. The Bazel build system has been modernized, with a cleaner root BUILD.bazel file and adoption of standard packaging rules. Additionally, there are updates to linting configurations, C++ code modernization, and a switch to Apple Silicon runners for macOS CI. While the scope of changes is vast, they appear to be well-structured improvements to the project's infrastructure. I have one suggestion to improve the robustness of the CI utility code.

[gemini-code-assist]

The global variable _RAYCI_BUILD_ID is initialized at module import time. This can cause issues in tests where os.environ is patched after import, as this variable will not be updated. This has led to incorrect assertions in several tests (e.g., test_linux_tester_container.py, test_windows_container.py). To make this more robust, RAYCI_BUILD_ID should be read from os.environ directly inside this function.

Suggested change

	def get_docker_image(docker_tag: str, build_id: Optional[str] = None) -> str:
	"""Get rayci image for a particular tag."""
	if not build_id:
	build_id = _RAYCI_BUILD_ID
	if build_id:
	return f"{_DOCKER_ECR_REPO}:{build_id}-{docker_tag}"
	return f"{_DOCKER_ECR_REPO}:{docker_tag}"
	def get_docker_image(docker_tag: str, build_id: Optional[str] = None) -> str:
	"""Get rayci image for a particular tag."""
	if not build_id:
	build_id = os.environ.get("RAYCI_BUILD_ID", "")
	if build_id:
	return f"{_DOCKER_ECR_REPO}:{build_id}-{docker_tag}"
	return f"{_DOCKER_ECR_REPO}:{docker_tag}"

[github-actions]

This pull request has been automatically marked as stale because it has not had
any activity for 14 days. It will be closed in another 14 days if no further activity occurs.
Thank you for your contributions.

You can always ask for help on our discussion forum or Ray's public slack channel.

If you'd like to keep this open, just leave any comment, and the stale label will be removed.