release: bump version to 0.6.2

[yzh119]

📌 Description

Bump version.

🔍 Related Issues

🚀 Pull Request Checklist

Thank you for contributing to FlashInfer! Before we review your pull request, please make sure the following items are complete.

✅ Pre-commit Checks

• I have installed pre-commit by running pip install pre-commit (or used your preferred method).
• I have installed the hooks with pre-commit install.
• I have run the hooks manually with pre-commit run --all-files and fixed any reported issues.

If you are unsure about how to set up pre-commit, see the pre-commit documentation.

🧪 Tests

• Tests have been added or updated as needed.
• All tests are passing (unittest, etc.).

Reviewer Notes

Summary by CodeRabbit

• Chores
  • Version bump to 0.6.2

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

[gemini-code-assist]

Summary of Changes

Hello @yzh119, 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 is a routine administrative update, solely focused on incrementing the project's version number. This change prepares the codebase for a new release or marks a development milestone, without introducing any functional code modifications or new features.

Highlights

• Version Update: The project version has been updated from 0.6.1 to 0.6.2 in version.txt.

🧠 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]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The version string in version.txt was updated from 0.6.1 to 0.6.2. This is a straightforward version number increment with no modifications to functionality or behavior.

Changes

Cohort / File(s)	Summary
Version Bump version.txt	Updated version identifier from 0.6.1 to 0.6.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• chore: bump version to v0.6.1 and exclude buggy apache-tvm-ffi releases #2347: Updates version.txt to bump project version
• update version to 0.6.0 #2300: Direct version string update in version.txt
• release: Bump version for v0.5.1 release #2031: Version string bump in version.txt

Poem

🐰 A version hops from 0.6.1 to 0.6.2,
A tiny leap, a rabbit's joyful spree!
One string revised, the changes oh so clean,
The smallest patch this codebase's ever seen!

---

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 correctly bumps the version to 0.6.2 in version.txt. My primary feedback is to also update CHANGELOG.md to document the changes for this release. Keeping the changelog synchronized with version releases is a crucial practice for informing users about new developments.

[gemini-code-assist]

With this version bump, please consider updating the CHANGELOG.md file to include an entry for version 0.6.2. This will help users understand the changes included in this release.

[claude]

PR Review: Version Bump to 0.6.2

✅ Overall Assessment

This PR is a straightforward version bump from 0.6.1 to 0.6.2, which is appropriate for a patch release. The change is minimal and correct.

📋 Review Findings

✅ Code Quality

• Clean and minimal: Single-line change in version.txt is exactly what's needed for a version bump
• Follows convention: Matches the project's versioning approach documented in CLAUDE.md

✅ Best Practices

• Semantic versioning: 0.6.1 → 0.6.2 is a patch-level bump, appropriate for backwards-compatible bug fixes and small features
• According to CLAUDE.md, patch releases include: "Small backwards-compatible features (new kernels, new SM support) and backwards-compatible bug fixes"
• The recent PRs merged since 0.6.1 appear to fit this criteria (hotfixes, CI improvements, bug fixes)

⚠️ Minor Observations

1. CHANGELOG.md Update

   • The CHANGELOG.md file currently only documents up to version 0.2.1
   • Recommendation: Consider updating CHANGELOG.md to document changes in 0.6.2 for better transparency and easier tracking of changes between versions
   • This would help users understand what's new/fixed in this release

2. Release Notes

   • Since this is a patch release, it would be helpful to have release notes summarizing the PRs merged since 0.6.1
   • Recent merged PRs include:
     • Hotfix: remove uv.lock (hotfix: remove uv.lock and add it to .gitignore #2399)
     • Feature: Add output_both_sf_layouts option (feat: Add output_both_sf_layouts option to add_rmsnorm_fp4quant API #2395)
     • Update Mamba API signature (Update Mamba selective_state_scan API signature #2392)
     • Fix: In-place Residual Update (fix: In-place Residual Update for add_rmsnorm_fp4quant #2385)
     • And several other CI/infrastructure improvements

✅ Security & Performance

• No security concerns for a version string change
• No performance implications

✅ Test Coverage

• Pre-commit checks passed ✓
• Tests marked as complete ✓
• Version string changes don't require additional test coverage

🎯 Summary

The version bump is technically correct and follows the project's conventions. The PR is ready for merge.

Suggestions for future releases:

• Consider maintaining CHANGELOG.md for versions beyond 0.2.x to provide better visibility into changes
• Consider automating changelog updates as part of the release process
• The "right-shifted" versioning scheme (major.minor.patch[.post1]) is well-documented in CLAUDE.md and being followed correctly

---

Review conducted following FlashInfer's CLAUDE.md guidelines and conventions.