chore: bump version to 0.0.3

[Kamilbenkirane]

Version bump for release v0.0.3

• Update version in pyproject.toml: 0.0.2 → 0.0.3
• Tag v0.0.3 has been created and publish workflow is running
• This PR merges the version bump to main for consistency

[claude]

Pull Request Review: Version Bump to 0.0.3

Summary

This PR updates the version number from 0.0.2 to 0.0.3 in pyproject.toml as part of the release process.

Code Quality ✅

Positive:

• Clean, minimal change focused on a single purpose
• Follows semantic versioning
• Commit message follows conventional commit format (chore: bump version to 0.0.3)
• PR description clearly explains the purpose and context

Best Practices ✅

Strengths:

• Version bump is isolated to its own PR
• PR description mentions that the tag has been created and publish workflow is running
• Merging to main for consistency is the right approach
• Single line change minimizes risk

Potential Issues ⚠️

Minor Observations:

1. Changelog Documentation: Consider whether a CHANGELOG.md should be updated alongside version bumps to document what changed in this release. This helps users understand what's new/fixed.

2. Release Notes: If not already automated, ensure that release notes are published with the v0.0.3 tag explaining what changed from v0.0.2.

3. Testing: For version bump PRs, verify that:

   • The package builds successfully (uv build)
   • The version number is correctly picked up in the built artifacts
   • No other files reference the old version string (e.g., docs, examples)

Security Concerns ✅

No security concerns for this change.

Performance Considerations ✅

No performance impact - this is a metadata change only.

Test Coverage 📋

Recommendations:

• While version bumps typically don't need dedicated tests, consider adding a simple test that validates __version__ attribute is accessible and matches pyproject.toml
• Ensure CI passes before merging (lint, type checking, unit tests)

Additional Recommendations

1. Automation: Consider automating version bumps using tools like:

   • bump2version or python-semantic-release
   • GitHub Actions that automatically create version bump PRs

2. Branch Protection: Ensure the publish workflow only runs on tags, not on release branches, to avoid duplicate publishes

3. Documentation: Update any version references in documentation or README if they exist

Verdict

Approved ✅

This is a straightforward, well-executed version bump. The change is minimal, focused, and follows good practices. No blocking issues identified.

---

Review generated by Claude Code