Update Docker CI tags to 20260105-a97b5d7

[flashinfer-bot]

This PR updates the Docker CI image tags to the latest version: 20260105-a97b5d7

Updated images:

• flashinfer/flashinfer-ci-cu126:20260105-a97b5d7
• flashinfer/flashinfer-ci-cu128:20260105-a97b5d7
• flashinfer/flashinfer-ci-cu129:20260105-a97b5d7
• flashinfer/flashinfer-ci-cu130:20260105-a97b5d7

Auto-generated by release-ci-docker workflow

Summary by CodeRabbit

• Chores
  • Updated Docker image tags in CI/CD pipeline configuration

_{✏️ 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 and dependencies, contributing to a more stable and up-to-date development pipeline.

Highlights

• Docker CI Image Tags: 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 20260105-a97b5d7.
• Automation: This update 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

Updated Docker image tags in ci/docker-tags.yml, changing the hash from 20251217-f059241 to 20260105-a97b5d7 for four CUDA versions (cu126, cu128, cu129, cu130). Repository paths remain unchanged; no control flow modifications.

Changes

Cohort / File(s)	Summary
Docker Tags Update ci/docker-tags.yml	Updated image tags for flashinfer-ci CUDA variants (cu126, cu128, cu129, cu130) to new hash 20260105-a97b5d7; all four entries modified consistently

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Possibly related PRs

• Update Docker CI tags to 20251217-f059241 #2231: Directly precedes this PR, transitioning from the old tag (20251217-f059241) to the new tag (20260105-a97b5d7) in the same file.
• Update Docker CI tags to 20251205-54c1678 #2179: Updates the same four Docker image tags in ci/docker-tags.yml with a different hash value.
• Update Docker CI tags to 20251203-1e15fed #2172: Modifies the same flashinfer CI image tag entries (cu126/cu128/cu129/cu130) with a different hash update.

Suggested reviewers

• cyx-6
• nvmbreughe
• yzh119

Poem

🐰 Hop hop! Docker tags take flight,
CUDA images, held just right,
From old hash to shiny new,
Four containers through and through,
Registry magic, fresh and bright! ✨🐇

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating Docker CI tags to a specific version hash.
Description check	✅ Passed	The description covers the main change and lists updated images, but is missing several required template sections like pre-commit checks and tests.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a97b5d7 and 4ef50ed.

📒 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: Docker tags updated consistently for all CUDA variants.

The ci/docker-tags.yml file correctly updates all four CUDA version images (cu126, cu128, cu129, cu130) to the new tag 20260105-a97b5d7. The YAML format is valid and the changes follow the existing usage pattern in Jenkinsfile where these tags are read and used to configure CI container runs.

---

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. My review focuses on improving the maintainability of the ci/docker-tags.yml file by suggesting the use of YAML anchors to avoid repeating the tag value. This adheres to the DRY (Don't Repeat Yourself) principle and will make future updates simpler and less error-prone.

[gemini-code-assist]

To improve maintainability and adhere to the DRY (Don't Repeat Yourself) principle, you can use a YAML anchor for the Docker tag. This way, the tag is defined in one place, making it easier to update in the future. This also simplifies the automation that generates these updates, as it would only need to change a single value.

Note: This suggestion uses a key .tag which is a convention for "hidden" keys in YAML that are often ignored by parsers but can be used for anchors. You may need to ensure your CI script that consumes this file can handle this format (e.g., by using a standard YAML parser).

.tag: &tag 20260105-a97b5d7
flashinfer/flashinfer-ci-cu126: *tag
flashinfer/flashinfer-ci-cu128: *tag
flashinfer/flashinfer-ci-cu129: *tag
flashinfer/flashinfer-ci-cu130: *tag

References

1. To improve maintainability and reduce redundancy, repeated values should be defined once and reused. This is commonly known as the Don't Repeat Yourself (DRY) principle.