bump version to 0.6.4

[aleozlx]

📌 Description

🔍 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 updated to 0.6.4.

• Documentation

  • Project changelog file removed.

[gemini-code-assist]

Summary of Changes

Hello @aleozlx, 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 primarily focuses on updating the project's version number. This change reflects a new release cycle, ensuring that all subsequent builds and deployments will correctly identify with the 0.6.4 version.

Highlights

• Version Bump: The project version has been updated from 0.6.3 to 0.6.4 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.

Changelog

• version.txt
  • Updated the version string from 0.6.3 to 0.6.4.

Activity

• No specific review comments or activity have been recorded for this pull request yet.

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]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Version in version.txt bumped from 0.6.3 to 0.6.4; CHANGELOG.md was deleted. No other code, logic, or configuration changes present.

Changes

Cohort / File(s)	Summary
Version file version.txt	Version updated from 0.6.3 → 0.6.4.
Changelog removal CHANGELOG.md	Entire file removed (all release history deleted).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• bump version to 0.6.3 #2497 — Prior sequential version bump affecting version.txt.
• release: bump version to 0.6.2 #2411 — Earlier version bump of version.txt.
• release: Bump version for v0.5.2 release #2057 — Another version.txt bump PR.

Suggested reviewers

• yzh119
• yongwww

Poem

🐰 A tiny hop, a tiny score,
From 0.6.3 to 0.6.4.
The changelog vanished, neat and light,
The version glows — just out of sight.
Hop on, release, and take your flight! 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description contains only the template structure with unfilled placeholder sections and no actual change details, context, or rationale for the version bump.	Fill in the Description section explaining why the version bump is needed, and provide relevant context for the changes (e.g., summary of CHANGELOG content removed).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'bump version to 0.6.4' accurately and specifically describes the main change in the pull request, which updates the version from 0.6.3 to 0.6.4 in version.txt.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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.}

[aleozlx]

/bot run

[gemini-code-assist]

Code Review

This pull request bumps the version in version.txt from 0.6.3 to 0.6.4. While the change is simple, it appears to be part of a release process. However, the CHANGELOG.md file has not been updated to reflect the changes for this new version. The changelog appears to be significantly out of date, with the latest entry being for version 0.2.1. It is crucial to maintain an up-to-date changelog for users to understand the evolution of the project. Please update the CHANGELOG.md with the details of this release. Additionally, the pull request description is currently empty; providing context for the version bump would be beneficial for reviewers.

[flashinfer-bot]

GitLab MR !318 has been created, and the CI pipeline #44066855 is currently running. I'll report back once the pipeline job completes.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@version.txt`:
- Line 1: CHANGELOG.md is outdated (only up to v0.0.7) while version.txt was
bumped to 0.6.4; update CHANGELOG.md by adding a new top-level release entry for
v0.6.4 including the date, a concise summary of the headline changes, migration
notes or breaking changes if any, and links or bullet points referencing the
relevant PRs/commits; ensure the new v0.6.4 section follows the existing
changelog format and ordering so the file now documents releases through v0.6.4
to match version.txt.

[aleozlx]

@flashinfer-bot run

[flashinfer-bot]

[SUCCESS] Pipeline #44066855: 16/20 passed

[aleozlx]

/bot run

[flashinfer-bot]

GitLab MR !318 has been updated with latest changes, and the CI pipeline #44263843 is currently running. I'll report back once the pipeline job completes.

[flashinfer-bot]

[FAILED] Pipeline #44263843: 15/20 passed

[aleozlx]

gitlab tests are clean
public ci failed tests are being rerun

[yongwww]

the test is passing.

I found the CHANGELOG.md was removed in the pr. cc: @yzh119

[yzh119]

@yongwww it's suggested by @sricketts .

I think it's a good idea considering the CHANGELOG.md is terribly outdated and our release note is very clear about changes.