Update Docker CI tags to 20260131-a52eff1

[flashinfer-bot]

This PR updates the Docker CI image tags to the latest version: 20260131-a52eff1

Updated images:

• flashinfer/flashinfer-ci-cu126:20260131-a52eff1
• flashinfer/flashinfer-ci-cu128:20260131-a52eff1
• flashinfer/flashinfer-ci-cu129:20260131-a52eff1
• flashinfer/flashinfer-ci-cu130:20260131-a52eff1

Auto-generated by release-ci-docker workflow

Summary by CodeRabbit

• Chores
  • Updated Docker image tags for CI build environments to the latest version across multiple CUDA configurations.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[gemini-code-assist]

Summary of Changes

Hello @flashinfer-bot, 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 ensures that the continuous integration environment utilizes the most current Docker images. By updating the image tags, the project benefits from the latest build configurations, dependencies, and potential fixes, thereby maintaining a robust and up-to-date CI pipeline for all future code integrations.

Highlights

• Docker CI Image Tag Update: The pull request updates the Docker CI image tags for flashinfer/flashinfer-ci-cu126, flashinfer/flashinfer-ci-cu128, flashinfer/flashinfer-ci-cu129, and flashinfer/flashinfer-ci-cu130.
• New Tag Version: All specified Docker images are updated to the tag 20260131-a52eff1 from the previous 20260114-cc1a362.
• Automated Generation: This pull request was automatically generated by the release-ci-docker workflow.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Docker image tags in the CI configuration are updated across four CUDA variant images (cu126, cu128, cu129, cu130) from commit hash 20260114-cc1a362 to 20260131-a52eff1, reflecting a newer build version for CI pipeline infrastructure.

Changes

Cohort / File(s)	Summary
Docker CI Image Tags ci/docker-tags.yml	Updated four flashinfer-ci CUDA images (cu126, cu128, cu129, cu130) to new tag version 20260131-a52eff1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update Docker CI tags to 20260114-cc1a362 #2351: Updates the same docker-tags.yml entries with a newer tag version for the same four CI images.
• Update Docker CI tags to 20260105-a97b5d7 #2289: Modifies the same ci/docker-tags.yml file updating Docker image tags for the identical four CUDA variant images.
• Update Docker CI tags to 20251104-d528f0c #2041: Updates the same ci/docker-tags.yml entries for flashinfer-ci-cu126, cu128, cu129, and cu130 images.

Suggested reviewers

• cyx-6
• nvmbreughe
• yzh119

Poem

🐰 Docker tags hop to the newest beat,
From old commits to timestamps so sweet,
CI containers dance with CUDA's might,
Four images leap into tomorrow's light! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the main change: updating Docker CI tags to a specific version (20260131-a52eff1).
Description check	✅ Passed	The PR description provides a clear explanation of what was changed and why, including which images were updated and that it was auto-generated by a workflow, though it lacks the required template sections.
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
• Commit unit tests in branch update-docker-tags-20260131-a52eff1

---

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 pull request, which appears to be automated, updates the Docker CI image tags to a new version. The changes are straightforward. I've added one suggestion to improve the maintainability of the ci/docker-tags.yml file. By using YAML anchors, the image tag is only defined once, which simplifies future updates and reduces the chance of inconsistencies. This would be a beneficial change to incorporate into the script that generates this file, assuming the file is processed by a standard YAML parser.

[gemini-code-assist]

To improve maintainability and reduce repetition, consider using YAML anchors and aliases, assuming the downstream tooling that consumes this file is a standard YAML parser. This would allow you to define the tag once and reuse it for all images. Since this file is auto-generated, this change would ideally be made in the script that produces this file.

flashinfer/flashinfer-ci-cu126: &tag 20260131-a52eff1
flashinfer/flashinfer-ci-cu128: *tag
flashinfer/flashinfer-ci-cu129: *tag
flashinfer/flashinfer-ci-cu130: *tag