Update Docker CI tags to 20260203-fb671fd

[flashinfer-bot]

This PR updates the Docker CI image tags to the latest version: 20260203-fb671fd

Updated images:

• flashinfer/flashinfer-ci-cu126:20260203-fb671fd
• flashinfer/flashinfer-ci-cu128:20260203-fb671fd
• flashinfer/flashinfer-ci-cu129:20260203-fb671fd
• flashinfer/flashinfer-ci-cu130:20260203-fb671fd

Auto-generated by release-ci-docker workflow

Summary by CodeRabbit

• Chores
  • Updated Docker images for CI pipeline supporting CUDA versions 126, 128, 129, and 130 to the latest image version. This ensures the build and test processes use current container images across all supported CUDA variants.

[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 focuses on maintaining the continuous integration environment by updating the Docker image tags to their most recent versions. This ensures that all CI pipelines operate with the latest dependencies and configurations, promoting consistency and reliability across the build and test processes.

Highlights

• Docker CI Image Tag Update: The Docker CI image tags have been updated to the latest version, 20260203-fb671fd.
• Specific Image Updates: This update applies to flashinfer/flashinfer-ci-cu126, flashinfer/flashinfer-ci-cu128, flashinfer/flashinfer-ci-cu129, and flashinfer/flashinfer-ci-cu130 images.
• Automated Generation: This PR 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.

Changelog

• ci/docker-tags.yml
  • Updated the Docker image tags for flashinfer/flashinfer-ci-cu126, flashinfer/flashinfer-ci-cu128, flashinfer/flashinfer-ci-cu129, and flashinfer/flashinfer-ci-cu130 from 20260203-9b5901e to 20260203-fb671fd.

Activity

• No specific human activity (comments, reviews) has been recorded for this pull request yet, as it appears to be an automated 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. ↩

[coderabbitai]

📝 Walkthrough

Walkthrough

This change updates four Docker image digest references in the CI configuration file. The entries for flashinfer/flashinfer-ci-cu126, cu128, cu129, and cu130 are updated from digest 9b5901e to fb671fd, consolidating all four tags to point to the same new image version.

Changes

Cohort / File(s)	Summary
Docker Image Tag Updates ci/docker-tags.yml	Updated image digests for four CUDA variant CI images (cu126, cu128, cu129, cu130) from 9b5901e to fb671fd.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update Docker CI tags to 20251205-54c1678 #2179: Updates the same four Docker image tag entries in ci/docker-tags.yml with a different digest update.
• Update Docker CI tags to 20251206-185d63a #2184: Modifies the identical flashinfer-ci-cu126/128/129/130 image references to align them to a new image digest.
• Update Docker CI tags to 20260131-a52eff1 #2457: Updates the same four CI Docker image tags to point to a newer unified image digest.

Suggested reviewers

• cyx-6
• nvmbreughe
• yzh119

Poem

🐰 A digest update hops our way,
Four cuda tags align in play,
From 9b59 to fb67's glow—
CI images are fresh, don't you know! 🐳

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating Docker CI image tags to a specific version identifier.
Description check	✅ Passed	The description provides clear context about the updates with specific image tags listed, but lacks some recommended template sections like pre-commit checks and test confirmations.
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-20260203-fb671fd

Important

Action Needed: IP Allowlist Update

If your organization protects your Git platform with IP whitelisting, please add the new CodeRabbit IP address to your allowlist:

• ✨ 136.113.208.247/32 (new)
• 34.170.211.100/32
• 35.222.179.152/32

Failure to add the new IP will result in interrupted reviews.

---

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 updates the Docker CI image tags. The change is straightforward and appears to be an automated update. I have one suggestion for the ci/docker-tags.yml file to improve its maintainability by reducing the repeated tag value. This would make future updates, even automated ones, cleaner and less prone to error.

[gemini-code-assist]

To improve maintainability and reduce redundancy, you can use YAML anchors to define the tag once and reuse it. This makes it easier to update the tag in the future, as it only needs to be changed in one place. If this file is auto-generated, it would be beneficial to update the generation script to produce this more maintainable format.

flashinfer/flashinfer-ci-cu126: &tag 20260203-fb671fd
flashinfer/flashinfer-ci-cu128: *tag
flashinfer/flashinfer-ci-cu129: *tag
flashinfer/flashinfer-ci-cu130: *tag

[yzh119]

#2467 doesn't change anything.