bump version for new release

[codelion]

This new version 0.0.16 will include all the test fixes and improvements we made, including:

• Fixed cascade validation tests
• Fixed island migration tests
• Fixed island tracking tests with proper bounds checking
• Improved database validation

[claude]

Claude finished @codelion's task —— View job

---

Code Review Complete ✅

Todo List:

• Read changed files (pyproject.toml and setup.py)
• Check for version consistency across files
• Review version bump approach and best practices
• Check for any potential security or quality issues
• Verify changes align with PR description
• Check repository guidelines (CLAUDE.md)
• Provide comprehensive review feedback

Review Feedback

✅ Positive Findings:

• Clean, straightforward version bump from 0.0.15 to 0.0.16
• Consistent version changes across both pyproject.toml and setup.py
• Minimal, focused changes with no unnecessary modifications
• No security concerns with simple version bumps

⚠️ Issues Identified:

1. Version Inconsistency (Critical)

• Issue: openevolve/__init__.py:5 contains __version__ = "0.1.0" which doesn't match the package version 0.0.16
• Impact: This creates confusion about the actual package version and can break version-dependent functionality
• Recommendation: Update __init__.py to match the package version, or establish a clear versioning strategy if they should differ

2. Missing Version Tracking (Minor)

• Issue: No CHANGELOG.md or version history documentation found
• Recommendation: Consider adding a changelog to track version history and release notes, especially since the PR description mentions specific improvements

3. Duplicate Version Declaration (Minor)

• Issue: Version is declared in both pyproject.toml and setup.py
• Recommendation: Consider using a single source of truth for version (e.g., import from __init__.py or use dynamic versioning)

Suggested Implementation:

# Option 1: Import from __init__.py in setup.py
from openevolve import __version__

setup(
    name="openevolve",
    version=__version__,
    ...
)

# Option 2: Dynamic versioning in pyproject.toml
[project]
dynamic = ["version"]

[tool.setuptools.dynamic]
version = {attr = "openevolve.__version__"}

Test Coverage: No test updates needed for version bumps, but consider adding version consistency tests.

Performance: No performance impact from version changes.

Security: No security concerns identified.

---

[codelion]

@claude can you please implement dynamic versioning in the project.

[claude]

Claude finished @codelion's task —— View job

---

Dynamic Versioning Implementation Complete ✅

Todo List:

• Read current project structure and understand existing files
• Check CLAUDE.md for repository guidelines
• Fix version inconsistency in init.py (update to 0.0.16)
• Implement dynamic versioning in pyproject.toml
• Update setup.py to import version from init.py
• Test the implementation
• Commit and push changes to PR branch

Summary of Changes

✅ Fixed Version Inconsistency:

• Updated openevolve/__init__.py:5 from __version__ = "0.1.0" to __version__ = "0.0.16"

✅ Implemented Dynamic Versioning:

• pyproject.toml: Replaced hardcoded version = "0.0.16" with dynamic = ["version"]
• pyproject.toml: Added [tool.setuptools.dynamic] section with version = {attr = "openevolve.__version__"}
• setup.py: Updated to import __version__ from openevolve module instead of hardcoding

✅ Single Source of Truth:

• Version is now declared only in openevolve/__init__.py
• Both pyproject.toml and setup.py dynamically read from this single source
• This prevents version drift and ensures consistency across all package declarations

✅ Committed Changes:

• Committed all changes with descriptive message
• Pushed to fix-debug-logging branch successfully

The implementation follows Python packaging best practices and ensures that future version bumps only require updating the version in one place: openevolve/__init__.py.

--- | Branch: fix-debug-logging

[CLAassistant]

All committers have signed the CLA.