Update Docker CI tags to 20260114-cc1a362

[flashinfer-bot]

This PR updates the Docker CI image tags to the latest version: 20260114-cc1a362

Updated images:

• flashinfer/flashinfer-ci-cu126:20260114-cc1a362
• flashinfer/flashinfer-ci-cu128:20260114-cc1a362
• flashinfer/flashinfer-ci-cu129:20260114-cc1a362
• flashinfer/flashinfer-ci-cu130:20260114-cc1a362

Auto-generated by release-ci-docker workflow

Summary by CodeRabbit

• Chores
  • Updated Docker image tags for continuous integration pipeline to latest versions.

_{✏️ 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 updates the Docker CI image tags to their latest versions. This ensures that the continuous integration pipelines utilize the most current build environments, promoting consistency and incorporating recent updates in the build infrastructure for all supported CUDA versions.

Highlights

• Docker CI Image Tags: Updated the Docker CI image tags for flashinfer/flashinfer-ci-cu126, flashinfer/flashinfer-ci-cu128, flashinfer/flashinfer-ci-cu129, and flashinfer/flashinfer-ci-cu130 to the latest version 20260114-cc1a362.

🧠 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

Four Docker image tag mappings in ci/docker-tags.yml are updated for flashinfer CI containers (cu126, cu128, cu129, cu130) from version 20260105-a97b5d7 to 20260114-cc1a362. No structural or logic changes occur.

Changes

Cohort / File(s)	Summary
Docker CI Tag Updates ci/docker-tags.yml	Updated four flashinfer-ci image tags: flashinfer-ci-cu126, flashinfer-ci-cu128, flashinfer-ci-cu129, and flashinfer-ci-cu130 changed from 20260105-a97b5d7 to 20260114-cc1a362

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Update Docker CI tags to 20251203-4efb7bb #2164: Updates the same four flashinfer CI Docker image tags with a different version string.
• Update Docker CI tags to 20251206-185d63a #2184: Modifies the identical ci/docker-tags.yml entries for the same flashinfer-ci image mappings.
• Update Docker CI tags to 20251203-1e15fed #2172: Directly updates the same four image entries (cu126, cu128, cu129, cu130) in ci/docker-tags.yml.

Suggested reviewers

• cyx-6
• nvmbreughe
• yzh119

Poem

🐰 Hop, hop! New image tags appear,
Four containers refreshed this year,
From January's old code bright,
To the latest January light! 🐳✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating Docker CI tags to a specific version number (20260114-cc1a362).
Description check	✅ Passed	The description provides the what, why, and relevant details, but omits the Description section heading and Related Issues section from the template.
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.}

---

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cc1a362 and 83d58c6.

📒 Files selected for processing (1)

• ci/docker-tags.yml

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-12-30T09:34:39.900Z

Learnt from: CR
Repo: flashinfer-ai/flashinfer PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-30T09:34:39.900Z
Learning: Applies to include/**/*.cuh : Kernel code in `include/flashinfer/` is automatically picked up by JIT compilation on changes - no pip reinstall needed

Applied to files:

• ci/docker-tags.yml

📚 Learning: 2025-12-30T09:34:39.900Z

Learnt from: CR
Repo: flashinfer-ai/flashinfer PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-30T09:34:39.900Z
Learning: Use `FLASHINFER_CUDA_ARCH_LIST` environment variable to specify target GPU architectures (e.g., '8.0 9.0a') and `FLASHINFER_NVCC_THREADS` to control parallel compilation threads

Applied to files:

• ci/docker-tags.yml

⏰ 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: LGTM!

The Docker CI image tag updates are consistent across all four CUDA version variants (cu126, cu128, cu129, cu130), and the tag format follows the expected YYYYMMDD-commitsha convention. Since this was auto-generated by the release-ci-docker workflow, the images should already be built and pushed.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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 to a new version. The change is straightforward and appears to be automated. I have provided one suggestion to improve the maintainability of the ci/docker-tags.yml file by using YAML anchors to avoid repeating the tag value. This will make future updates simpler and less prone to error.

[gemini-code-assist]

To improve maintainability and reduce redundancy, consider using a YAML anchor for the Docker tag. This defines the tag in one place, so future updates only require changing a single line. This reduces the chance of inconsistencies, especially if manual edits are ever needed.

ci_tag: &ci_tag 20260114-cc1a362
flashinfer/flashinfer-ci-cu126: *ci_tag
flashinfer/flashinfer-ci-cu128: *ci_tag
flashinfer/flashinfer-ci-cu129: *ci_tag
flashinfer/flashinfer-ci-cu130: *ci_tag