v0.1.34 - Code Cleanup & Constants Refactoring (2025-12-13)¶
What Changed?¶
This release removes 10 unused constants from the codebase and cleans up the public API exports. The refactoring reduces code clutter and clarifies which constants are part of the public interface. All functionality remains unchangedβthis is purely a maintenance release to improve code quality.
What's New¶
Cleanup: Removed Unused Constants¶
What it does: This release removes constants that were defined but never used in the codebase. This includes timeout configurations, retry settings, and response key constants that were placeholder implementations.
Why it matters: Keeping unused constants clutters the codebase and confuses developers about what's actually in use. Removing them makes the remaining constants more meaningful and the API clearer.
Removed constants:
COMMAND_TIMEOUT_MS,RESPONSE_TIMEOUT_MS,COMMAND_BUFFER_SIZEMAX_RETRIES,RETRY_DELAY_MSRESPONSE_FIELD_TYPE_KEY,RESPONSE_STATUS_KEYSTATUS_OK,STATUS_ERRORDEFAULT_TIMEOUT_RETRIES
Public API simplification:
- Removed
FIELD_TYPE_MOCKfrom__init__.pyexports (internal tomock.py)
Installation¶
Quick Start¶
# Get the release
git checkout vX.Y.Z
# Setup
task env:setup
# Run CLI
uv run kazunoko --help
What's Different from the Last Version?¶
β Added¶
- None (maintenance release)
π§ Changed¶
- Removed 10 unused constants from
constants.py - Removed
FIELD_TYPE_MOCKfrom public API exports in__init__.py - Public API now exports only 5 constants (down from 6)
π Fixed¶
- Code clarity: removed constants that were never used
Is It Safe to Upgrade?¶
Backward Compatible: Yes
- This is a pure refactoring release with no functional changes
- Removed constants were not part of the public API usage
- All existing code continues to work without modification
FIELD_TYPE_MOCKremoval only affects users who directly imported it (not recommended)
Tests Passed¶
- β Builds without errors
- β Type checking (mypy) - no new errors
- β Linting (ruff) - all checks passed
- β No remaining references to removed constants
Release Details¶
- Date: 2025-12-13
- Version: v0.1.34
- Files Changed: 2
- Commits:
988a880
Next Steps¶
- Future releases will continue to focus on code quality and maintainability
- Potential areas for investigation: hardcoded strings and response marker optimization
- Consider adding test suite for improved coverage