Update Docker CI tags to 20251217-f059241

[flashinfer-bot]

This PR updates the Docker CI image tags to the latest version: 20251217-f059241

Updated images:

• flashinfer/flashinfer-ci-cu126:20251217-f059241
• flashinfer/flashinfer-ci-cu128:20251217-f059241
• flashinfer/flashinfer-ci-cu129:20251217-f059241
• flashinfer/flashinfer-ci-cu130:20251217-f059241

Auto-generated by release-ci-docker workflow

Summary by CodeRabbit

• Chores
  • Updated CI/CD pipeline container image references for internal infrastructure.

Note: This release contains only internal infrastructure updates with no user-facing changes.

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

[coderabbitai]

Walkthrough

Updated four Docker image references in ci/docker-tags.yml for flashinfer CI containers (cu126, cu128, cu129, cu130) from tag 20251206-185d63a to 20251217-f059241. No functional logic or error handling modifications.

Changes

Cohort / File(s)	Change Summary
CI Docker Tags ci/docker-tags.yml	Updated image tags for four flashinfer CI containers (cu126, cu128, cu129, cu130) from 20251206-185d63a to 20251217-f059241

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify that the new image tags (20251217-f059241) reference valid, functional Docker images
• Confirm all four CUDA version variants (cu126, cu128, cu129, cu130) are correctly updated with consistent tag values

Possibly related PRs

• Update Docker CI tags to 20251206-185d63a #2184: Updates the same four flashinfer-ci Docker image tags in ci/docker-tags.yml to different values
• Update Docker CI tags to 20251205-54c1678 #2179: Modifies the identical ci/docker-tags.yml entries for the four flashinfer-ci-cu12* images with a different tag update
• Update Docker CI tags to 20251204-cdc5fb7 #2176: Updates the same ci/docker-tags.yml entries for the four flashinfer-ci-cu{126,128,129,130} images with alternate tag values

Suggested reviewers

• cyx-6
• nvmbreughe
• yzh119

Poem

🐰 A rabbit pulled the tag update thread,
Four images dressed in new threads instead,
From old digests to fresh ones so bright,
The CI containers now gleam in the light! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and clearly summarizes the main change: updating Docker CI image tags to a specific version.
Description check	✅ Passed	The description covers the main purpose, lists the updated images, and cites the auto-generation source. However, it lacks the recommended template sections like Related Issues and Pre-commit Checks.
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-20251217-f059241

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f059241 and 0d04361.

📒 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: Tag updates are consistent across all CUDA versions.

All four Docker CI image tags have been updated to 20251217-f059241 across CUDA versions 12.6, 12.8, 12.9, and 13.0. The automated update maintains uniformity as expected.

---

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 performs a routine update of the Docker CI image tags to their latest versions. This ensures that the continuous integration environment consistently uses the most recent dependencies and configurations, which is crucial for maintaining the stability and reliability of the build and test pipelines.

Highlights

• Docker CI Image Tags Updated: The Docker CI image tags have been updated to the latest version, 20251217-f059241.
• Affected Images: This update applies to the flashinfer/flashinfer-ci-cu126, flashinfer/flashinfer-ci-cu128, flashinfer/flashinfer-ci-cu129, and flashinfer/flashinfer-ci-cu130 Docker images.
• Automated Generation: This pull request was automatically generated by the release-ci-docker workflow to ensure routine updates.

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, as noted in the description, auto-generated. I have one suggestion to improve the maintainability of the ci/docker-tags.yml file by using YAML anchors to avoid repeating the same tag, which would make future updates easier to manage. This would likely require an update to the script that generates this file.

[gemini-code-assist]

To improve maintainability and adhere to the DRY (Don't Repeat Yourself) principle, consider using YAML anchors and aliases. This approach defines the tag once and reuses it for the other images. This makes future updates simpler and less prone to copy-paste errors. Since this file is auto-generated, this change would ideally be implemented in the script that creates this file.

flashinfer/flashinfer-ci-cu126: &ci_tag 20251217-f059241
flashinfer/flashinfer-ci-cu128: *ci_tag
flashinfer/flashinfer-ci-cu129: *ci_tag
flashinfer/flashinfer-ci-cu130: *ci_tag

References

1. The DRY (Don't Repeat Yourself) principle is a fundamental software development principle aimed at reducing repetition of information. In this case, the Docker image tag is repeated four times. Consolidating it would improve maintainability.