release: Bump version for v0.5.1 release

[bkryu]

📌 Description

Update version.txt

🔍 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.5.1

[coderabbitai]

Walkthrough

The version number in version.txt is bumped from 0.5.0 to 0.5.1. No functional code changes or logic modifications are included in this update.

Changes

Cohort / File(s)	Summary
Version Bump version.txt	Version updated from 0.5.0 to 0.5.1

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• release: Bump version for v0.5.0rc1 release; #2008: Previous version bump PR that modified the same file to set version to 0.5.0; this PR continues the versioning sequence to 0.5.1.

Suggested reviewers

• yzh119

Poem

🐰 A patch is born, so small and neat,
Point-one ascends, the version's beat,
No code was changed, just numbers flow,
The version climbs, a gentle glow! ✨

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: bumping the version to v0.5.1, which is the only modification in this pull request.
Description check	✅ Passed	The description follows the template structure with all sections present. The Description section clearly states the change, the Related Issues section is appropriately left empty with only comments, the Pre-commit Checks are all marked complete with all boxes checked, and Tests section confirms tests are passing.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 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 1e75bff and 837af23.

📒 Files selected for processing (1)

• version.txt (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)

version.txt (1)

1-1: No action needed—version propagation is already handled by the build system.

The version.txt change to 0.5.1 is the only change required. All three build backends (root, flashinfer-cubin, flashinfer-jit-cache) are correctly configured to read version.txt and automatically generate synchronized versions in their respective _build_meta.py files. The deprecation warning strings referencing "v0.5.0" in core.py are intentional and should remain unchanged.

---

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]

Summary of Changes

Hello @bkryu, 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 prepares the repository for the v0.5.1 release by updating the project's version identifier. This is a routine maintenance step to ensure that the codebase accurately reflects its current release status.

Highlights

• Version Update: The project version has been updated from "0.5.0" to "0.5.1" in version.txt to reflect the upcoming release.

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

[gemini-code-assist]

Code Review

This pull request correctly bumps the version in version.txt from 0.5.0 to 0.5.1. However, for a version release, it's crucial to also update the project's changelog. I noticed that CHANGELOG.md does not contain an entry for v0.5.1, and its latest documented version is v0.2.1. To ensure users are aware of the new features, bug fixes, and other changes in this release, please consider adding a corresponding entry for v0.5.1 to the changelog.