Hotfix | Bump version to 0.5.0

[yuval-qf]

Description

Motivation and Context

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🎨 Code style/refactoring (no functional changes)
• 🧪 Test updates
• 🔧 Configuration/build changes

Changes Made

Screenshots/Examples (if applicable)

Checklist

• I have read the CONTRIBUTING.md guide
• My code follows the code style of this project (PEP 8, type hints, docstrings)
• I have run uv run black . to format my code
• I have run uv run flake8 . and fixed all issues
• I have run uv run mypy --config-file .mypy.ini . and addressed type checking issues
• I have run uv run bandit -c .bandit.yaml -r . for security checks
• I have added tests that prove my fix is effective or that my feature works
• I have run uv run pytest and all tests pass
• I have manually tested my changes
• I have updated the documentation accordingly
• I have added/updated type hints for new/modified functions
• My changes generate no new warnings
• I have checked my code for security issues
• Any dependent changes have been merged and published

Testing

Test Configuration:

• Python version:
• OS:
• Other relevant details:

Test Steps:
1.
2.
3.

Additional Notes

Related Issues/PRs

• Fixes #
• Related to #
• Depends on #

---

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b049b3d7-4250-48a5-9d08-47abbca29d1d

📥 Commits

Reviewing files that changed from the base of the PR and between 5cc1f17 and f9e3b04.

📒 Files selected for processing (1)

• VERSION

🚧 Files skipped from review as they are similar to previous changes (1)

• VERSION

---

Summary by CodeRabbit

• Chores
  • Version bumped to 0.5.0.
  • No functional, behavioral, or structural changes; release only updates version metadata for tracking. Users should expect no change in functionality or behavior. Estimated review effort: low.

Walkthrough

This pull request updates the project's VERSION file, bumping the release from 0.4.1 to 0.5.0. The change is limited to the version string; no code, configuration, or functionality was modified.

Changes

Cohort / File(s)	Summary
Version Bump VERSION	Updated version string from 0.4.1 to 0.5.0 (single-line change).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• Bump version to 0.2.0 #124: Also modifies the VERSION file to bump the project version (single-line version string change).
• Hotfix | Bump version to 0.2.2 #131: Updates the repository VERSION file with a single-line version bump.
• Hotfix | Bump version to 0.3.4 #152: Single-line VERSION file update to bump release number.

Suggested reviewers

• drorIvry

Poem

🐰
I nudged a digit, gave the number a lift,
From 0.4.1 to 0.5.0 — a tiny gift.
No code to rewrite, no tests to run,
Just a hop in the ledger and then I’m done.

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title claims a hotfix to bump version to 0.4.2, but the actual change bumps to 0.5.0, creating a significant discrepancy between the stated and actual changes.	Update the PR title to accurately reflect the version bump to 0.5.0, or correct the commit to match the intended 0.4.2 version if that was the goal.
Description check	⚠️ Warning	The PR description is entirely templated with no actual content filled in; all sections remain empty or unchecked, providing no explanation of the version bump rationale or changes.	Complete the description by filling in the Description, Motivation and Context, and Type of Change sections, and provide details about why the version was bumped and what this release includes.

✅ Passed checks (1 passed)

Check name	Status	Explanation
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
• Commit unit tests in branch hotfix/bump-version-to-0-4-2

📝 Coding Plan

• Generate coding plan for human review comments

---

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