Hotfix | Bump version to 0.2.2

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

Summary by CodeRabbit

• Chores
  • Version updated to 0.2.2 (maintenance release)

Walkthrough

The VERSION file is updated to increment the version string from 0.2.1 to 0.2.2. This is a patch-level version bump with no modifications to code logic or behavior.

Changes

Cohort / File(s)	Change Summary
Version Bump VERSION	Increments version string from 0.2.1 to 0.2.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• Bump version to 0.2.1 #127: Both PRs perform a direct version-string bump in the same project.
• Bump version to 0.2.0 #124: Both PRs update only the VERSION file to bump the package version incrementally.

Suggested reviewers

• drorIvry

Poem

🐰 A whisker-twitch and hop of glee,
From point-two-one to point-two-three!
The version climbs, so small yet neat,
A patch update, a dev's sweet treat! 🌟

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is entirely empty/templated with no substantive content filled in, leaving critical sections like Description, Motivation and Context, Type of Change, Changes Made, and Related Issues/PRs blank or as placeholders.	Fill in key sections: provide a brief description of the version bump, explain the motivation/reason for the hotfix, check the appropriate Type of Change, list the actual changes made, and link any related issues.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Hotfix | Bump version to 0.2.2' directly and clearly describes the main change: bumping the version string from 0.2.1 to 0.2.2, which aligns with the AI-generated summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch hotfix/bump-version-to-0-2-2

---

📜 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 bb97862 and f634176.

📒 Files selected for processing (1)

• VERSION (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). (2)

• GitHub Check: rogue_sanity
• GitHub Check: codestyle

🔇 Additional comments (2)

VERSION (2)

1-1: Version bump format is correct.

The patch-level version bump from 0.2.1 to 0.2.2 follows semantic versioning conventions and is appropriate for a hotfix.

---

1-1: Version consistency verified across codebase.

All version references are properly synchronized:

• VERSION file: 0.2.2 ✓
• Python packages (pyproject.toml, sdks/python/pyproject.toml): Use dynamic versioning that automatically references the VERSION file, ensuring they will be 0.2.2
• JavaScript examples: Maintain independent versions (1.0.0), which is the correct pattern for example packages

The codebase architecture properly handles version management with no stale or inconsistent references found.

---

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