Update Docker CI tags to 20251204-cdc5fb7

[flashinfer-bot]

This PR updates the Docker CI image tags to the latest version: 20251204-cdc5fb7

Updated images:

• flashinfer/flashinfer-ci-cu126:20251204-cdc5fb7
• flashinfer/flashinfer-ci-cu128:20251204-cdc5fb7
• flashinfer/flashinfer-ci-cu129:20251204-cdc5fb7
• flashinfer/flashinfer-ci-cu130:20251204-cdc5fb7

Auto-generated by release-ci-docker workflow

Summary by CodeRabbit

• Chores
  • Updated CI Docker image configurations for internal infrastructure maintenance.

---

Note: This release contains no user-facing changes.

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

[coderabbitai]

Walkthrough

Docker image tags updated from 20251203-1e15fed to 20251204-cdc5fb7 for four CUDA variant CI images (cu126, cu128, cu129, cu130) in the configuration file.

Changes

Cohort / File(s)	Change Summary
Docker CI Image Tag Updates ci/docker-tags.yml	Updated four flashinfer-ci Docker image tag mappings from 20251203-1e15fed to 20251204-cdc5fb7 for CUDA variants cu126, cu128, cu129, and cu130

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• #2158: Updates the same four flashinfer-ci image tag mappings in ci/docker-tags.yml with different tag values
• #2164: Modifies the same ci/docker-tags.yml entries to update Docker image tags for the four flashinfer-ci images
• #2172: Updates the same ci/docker-tags.yml entries, changing tags between versions 20251203-1e15fed and 20251204-cdc5fb7

Suggested reviewers

• cyx-6
• nvmbreughe
• yzh119

Poem

🐰 A tag update swift and clean,
Four CUDA variants now convene,
From old to new the images dance,
CI workflows get their chance,
Docker magic, small but keen! 🐳

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: updating Docker CI tags to a specific version. It is directly related to the changeset.
Description check	✅ Passed	The description includes what was changed and why, but is missing the template's required sections like pre-commit checks, tests checklist, and related issues.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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-20251204-cdc5fb7

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cdc5fb7 and ff35d2b.

📒 Files selected for processing (1)

• ci/docker-tags.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Deploy Docs

🔇 Additional comments (1)

ci/docker-tags.yml (1)

1-4: Docker CI tags updated correctly.

All four CUDA variant images are updated consistently with the new tag 20251204-cdc5fb7. The format is valid YAML, all expected images are present (cu126, cu128, cu129, cu130), and the tag values match the PR objectives.

---

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]

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 recent Docker images by updating their version tags. This keeps the build and test processes aligned with the latest specified dependencies and configurations, contributing to a stable and up-to-date development pipeline.

Highlights

• Docker CI 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 Version: All updated images now point to the version 20251204-cdc5fb7.
• Automation: This update was automatically generated by the release-ci-docker workflow.

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 updates the Docker CI image tags to a new version. The change is straightforward and appears to be part of an automated process. I have one suggestion to improve the maintainability of ci/docker-tags.yml by using YAML anchors to avoid duplicating the version tag. This would make future updates simpler and less prone to error.

[gemini-code-assist]

To improve maintainability and avoid duplicating the docker tag, consider using YAML anchors. This would define the tag once on the first image and then reference it for all subsequent images. This makes future updates easier and less error-prone. Since this file is auto-generated, this change would need to be made in the workflow that creates this PR.

flashinfer/flashinfer-ci-cu126: &docker_tag 20251204-cdc5fb7
flashinfer/flashinfer-ci-cu128: *docker_tag
flashinfer/flashinfer-ci-cu129: *docker_tag
flashinfer/flashinfer-ci-cu130: *docker_tag

[yzh119]

/bot run

[flashinfer-bot]

GitLab MR !178 has been created, and the CI pipeline #39639189 is currently running. I'll report back once the pipeline job completes.