release: Bump version for v0.5.0rc1 release;

[bkryu]

📌 Description

Update version in version.txt to v0.5.0 as we prepare for v0.5.0rc1 release.

🔍 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.5.0 (no functional changes)

[coderabbitai]

Walkthrough

The version string in version.txt is updated from 0.4.1 to 0.5.0. This is a version bump with no logic, error handling, or control flow modifications.

Changes

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

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰 A hop, a skip, from point-four to five,
The version string grows, keeping code alive,
No logic bent, no errors fret,
Just numbers dancing—version reset! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "release: Bump version for v0.5.0rc1 release;" clearly and directly describes the main change in the changeset. The raw_summary confirms the change is a version bump from 0.4.1 to 0.5.0 with no logic changes, which matches the title's focus on bumping the version for a release. The title is concise, specific, and provides enough information for a teammate to understand the primary change when scanning commit history.
Description Check	✅ Passed	The pull request description follows the repository template structure with all critical sections appropriately completed. The Description section clearly explains the change (updating version.txt to v0.5.0 for the v0.5.0rc1 release), the Pre-commit Checks section has all three items marked as complete with checkboxes, and the Tests section indicates that tests were updated and are passing. The Related Issues and Reviewer Notes sections are empty, but these are not critical for this type of straightforward version bump and the Related Issues section is naturally empty when there are no related issues.

✨ 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 6a962ef and d8778bc.

📒 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: Verify version string matches release strategy.

The version in version.txt is 0.5.0, but the PR title mentions "v0.5.0rc1 release". Clarify whether:

• 0.5.0 is intentional (with v0.5.0rc1 being only a git tag/branch label), or
• This should be 0.5.0rc1 to match the release candidate designation.

Additionally, verify that other version-dependent files in the codebase (e.g., pyproject.toml, setup.py, __init__.py, or similar) have been updated consistently with this bump, if applicable.

The version string format 0.5.0 follows semantic versioning conventions. Once the version strategy is confirmed, this change looks good.

---

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

[yzh119]

Last step of the workflow failed because update_whl_index script didn't recognize rc versions:

• https://github.com/flashinfer-ai/flashinfer/actions/runs/18929490991/job/54049304551

A bugfix was created in #2009 , and the wheel index was updated manually: flashinfer-ai/whl@3f5a6d5