chore: bump version to 0.0.4

[Kamilbenkirane]

Bump version to 0.0.4 to prepare for release with text-generation package.

After merge, create tag v0.0.4 to trigger publish workflow.

[claude]

PR Review: Version Bump to 0.0.4

Summary

This PR bumps the version from 0.0.3 to 0.0.4 in both the main package (celeste-ai) and the text-generation sub-package. The changes are minimal and focused solely on version updates in preparation for a new release.

---

✅ Code Quality & Best Practices

Positive aspects:

• Clean, focused change with a single responsibility (version bump)
• Follows semantic versioning convention
• Consistent version updates across both packages (main + text-generation)
• Clear commit message following conventional commits format (chore: bump version to 0.0.4)
• PR description includes clear next steps (create tag v0.0.4)

Observations:

• Both pyproject.toml files are properly updated
• Version consistency is maintained across the monorepo workspace

---

🐛 Potential Issues

Critical: Missing CHANGELOG or Release Notes

Severity: Medium

The repository does not appear to have a CHANGELOG.md file to document what changes are included in version 0.0.4. While the publish workflow (.github/workflows/publish.yml:130-142) auto-generates release notes from git commits, maintaining a proper CHANGELOG would provide better context for users.

Recommendation:
Consider adding a CHANGELOG.md file to track version history, especially since this is an early-stage library (0.0.x). This helps users understand:

• What features/fixes are included in each release
• Breaking changes (important even in 0.0.x versions)
• Migration paths between versions

Version Synchronization Concern

Severity: Low

The main package (celeste-ai) and sub-package (text-generation) share the same version number. While this is fine for 0.0.x releases, consider whether these packages should have independent versioning in the future, especially if:

• The text-generation package stabilizes before other capabilities
• You want to release updates to one package without affecting others
• Different packages have different release cadences

Current approach: Both packages share version 0.0.4 (synchronized)
Alternative: Independent versioning per package (e.g., celeste-ai@0.0.4, text-generation@0.1.0)

---

⚡ Performance Considerations

N/A - Version number changes have no runtime performance impact.

---

🔒 Security Concerns

None identified. The changes are purely metadata updates with no security implications.

The publish workflow includes good security practices:

• Uses trusted PyPI publish action with OIDC (id-token: write)
• Validates version consistency between git tag and pyproject.toml
• Publishes to TestPyPI before production PyPI
• Runs full CI/CD pipeline including security scans before publishing

---

🧪 Test Coverage

Observations:

• No tests need to be added for version number changes
• The publish workflow will run the full CI/CD pipeline (format, lint, typecheck, security scan, unit tests, integration tests)
• Version validation in the publish workflow ensures tag matches pyproject.toml version (.github/workflows/publish.yml:32-37)

Recommendation:
After merging this PR and creating the v0.0.4 tag, verify:

1. CI pipeline passes on the tag
2. Integration tests succeed (they run before publish)
3. TestPyPI publish succeeds
4. Production PyPI publish completes successfully

---

📋 Pre-Merge Checklist

Before merging and tagging:

• Verify this PR includes all intended changes for 0.0.4
• Confirm no other PRs should be included in this release
• Review git log since last release to ensure release notes will be accurate
• Consider documenting changes in a CHANGELOG.md (recommended)
• After merge, create tag using: git tag -a v0.0.4 -m "Release v0.0.4" then git push origin v0.0.4
• Monitor the publish workflow for any issues

---

🎯 Post-Merge Actions

The PR description correctly notes that after merge, you should:

1. Create git tag v0.0.4 on the merge commit
2. Push the tag to trigger the publish workflow
3. Monitor the workflow execution
4. Verify packages appear on PyPI:
   • https://pypi.org/project/celeste-ai/0.0.4/
   • https://pypi.org/project/text-generation/0.0.4/
5. Check the GitHub Release is created automatically

---

💡 Overall Assessment

Status: ✅ Approved with Suggestions

This is a clean, straightforward version bump PR. The changes are correct and follow good practices. The main suggestions are:

1. Consider adding a CHANGELOG.md for better version history tracking
2. Evaluate versioning strategy for future releases (synchronized vs. independent)

The code quality is excellent, no bugs or security issues were found, and the automated publish workflow appears robust.

---

Great work on the release preparation! 🚀

Review generated with assistance from Claude Code