Skip to content

Update Docker CI tags to 20251203-4efb7bb#2164

Merged
yzh119 merged 1 commit intomainfrom
update-docker-tags-20251203-4efb7bb
Dec 3, 2025
Merged

Update Docker CI tags to 20251203-4efb7bb#2164
yzh119 merged 1 commit intomainfrom
update-docker-tags-20251203-4efb7bb

Conversation

@flashinfer-bot
Copy link
Collaborator

@flashinfer-bot flashinfer-bot commented Dec 3, 2025

This PR updates the Docker CI image tags to the latest version: 20251203-4efb7bb

Updated images:

  • flashinfer/flashinfer-ci-cu126:20251203-4efb7bb
  • flashinfer/flashinfer-ci-cu128:20251203-4efb7bb
  • flashinfer/flashinfer-ci-cu129:20251203-4efb7bb
  • flashinfer/flashinfer-ci-cu130:20251203-4efb7bb

Auto-generated by release-ci-docker workflow

Summary by CodeRabbit

  • Chores
    • Updated container images in deployment pipeline to the latest version.

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

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @flashinfer-bot, I'm Gemini Code Assist1! 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 CI image tags to their latest available versions. This ensures that all CI pipelines run with the most recent build configurations and dependencies, promoting consistency and leveraging any improvements or fixes in the updated images.

Highlights

  • Docker CI Image Tags Update: The Docker CI image tags for flashinfer/flashinfer-ci-cu126, flashinfer/flashinfer-ci-cu128, flashinfer/flashinfer-ci-cu129, and flashinfer/flashinfer-ci-cu130 have been updated to 20251203-4efb7bb from their previous version 20251202-23ff744.
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
Copy link
Contributor

coderabbitai bot commented Dec 3, 2025

Walkthrough

Docker image tags in the CI configuration file updated from 20251202-23ff744 to 20251203-4efb7bb across four CUDA version entries (cu126, cu128, cu129, cu130). Only tag values changed; image names and configuration structure remain unchanged.

Changes

Cohort / File(s) Summary
Docker CI Image Tag Updates
ci/docker-tags.yml
Updated docker image digest/tags from 20251202-23ff744 to 20251203-4efb7bb for all four CUDA images (cu126, cu128, cu129, cu130)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Single file modified with homogeneous tag updates across four entries
  • Verify that tag digests are correct and intentionally updated to the new version

Possibly related PRs

Suggested reviewers

  • cyx-6
  • nvmbreughe
  • yzh119

Poem

🐰 Four CUDA paths hop through the night,
Tags digest swapped for new delight—
Twenty-five to twenty-three,
Docker dancing, wild and free! 🐳✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description check ❓ Inconclusive The description provides context and details about the changes, though it does not follow the template structure with sections like 'Description', 'Related Issues', and 'Checklist'. Consider using the repository's PR template with sections for Description, Related Issues, and Checklist items to improve consistency and clarity.
✅ Passed checks (2 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.
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-20251203-4efb7bb

📜 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 4efb7bb and 5321e6f.

📒 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 tags consistently updated across all CUDA versions.

All four image tags updated uniformly to 20251203-4efb7bb across cu126, cu128, cu129, and cu130 variants. The tag format (date + commit hash) is correct and YAML syntax is valid.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request automatically updates the Docker CI image tags to a new version. The change is straightforward. I've added one suggestion to improve the maintainability of the docker-tags.yml file by using YAML anchors to avoid repeating the tag, which would make future updates easier.

Comment on lines +1 to +4
flashinfer/flashinfer-ci-cu126: 20251203-4efb7bb
flashinfer/flashinfer-ci-cu128: 20251203-4efb7bb
flashinfer/flashinfer-ci-cu129: 20251203-4efb7bb
flashinfer/flashinfer-ci-cu130: 20251203-4efb7bb
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To improve maintainability and avoid repeating the same Docker tag, you can use YAML anchors and aliases. This way, you only need to update the tag in one place for future changes. Since this PR is auto-generated, this improvement could be applied to the script that generates this file.

flashinfer/flashinfer-ci-cu126: &tag 20251203-4efb7bb
flashinfer/flashinfer-ci-cu128: *tag
flashinfer/flashinfer-ci-cu129: *tag
flashinfer/flashinfer-ci-cu130: *tag

@yzh119 yzh119 enabled auto-merge (squash) December 3, 2025 03:57
@yzh119 yzh119 merged commit 442dec9 into main Dec 3, 2025
4 checks passed
@yzh119 yzh119 deleted the update-docker-tags-20251203-4efb7bb branch December 3, 2025 06:33
juju812 pushed a commit to juju812/flashinfer that referenced this pull request Dec 4, 2025
This PR updates the Docker CI image tags to the latest version:
`20251203-4efb7bb`

Updated images:
- flashinfer/flashinfer-ci-cu126:20251203-4efb7bb
- flashinfer/flashinfer-ci-cu128:20251203-4efb7bb
- flashinfer/flashinfer-ci-cu129:20251203-4efb7bb
- flashinfer/flashinfer-ci-cu130:20251203-4efb7bb

Auto-generated by [release-ci-docker
workflow](https://github.com/flashinfer-ai/flashinfer/actions/runs/19879133946)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Updated container images in deployment pipeline to the latest version.

<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: yzh119 <11773619+yzh119@users.noreply.github.com>
BingooYang pushed a commit to BingooYang/flashinfer that referenced this pull request Mar 13, 2026
This PR updates the Docker CI image tags to the latest version:
`20251203-4efb7bb`

Updated images:
- flashinfer/flashinfer-ci-cu126:20251203-4efb7bb
- flashinfer/flashinfer-ci-cu128:20251203-4efb7bb
- flashinfer/flashinfer-ci-cu129:20251203-4efb7bb
- flashinfer/flashinfer-ci-cu130:20251203-4efb7bb

Auto-generated by [release-ci-docker
workflow](https://github.com/flashinfer-ai/flashinfer/actions/runs/19879133946)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Updated container images in deployment pipeline to the latest version.

<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: yzh119 <11773619+yzh119@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants