Conversation
added 6 commits
November 10, 2025 14:19
Implement automated version management system with pyproject.toml as single source of truth for version numbers. Features: - scripts/get_version.py: Extract version from pyproject.toml - scripts/bump_version.py: Automated semantic version bumping - Supports major, minor, patch bumps - Auto-updates CHANGELOG.md with version and date - Dry-run mode for preview - Makefile targets: version, bump-patch, bump-minor, bump-major - Comprehensive documentation in docs/VERSION_MANAGEMENT.md Benefits: - Eliminates version number duplication across files - Automates changelog updates - Prevents version mismatches - Streamlines release workflow - Supports semantic versioning Usage: make version # Show current version make bump-patch # Bump patch: 0.3.2 → 0.3.3 python3 scripts/bump_version.py minor --dry-run # Preview changes
Merge latest changes from main including: - Version 0.3.2 release with devcontainer prerequisites validation - Version 0.3.1 documentation updates - Updated README with comprehensive prerequisites section - Enhanced setup-user-conf.sh with environment variable support Resolved conflict in CHANGELOG.md by accepting main's release history.
Update version from 0.3.2 to 0.3.3 for version management system release. Updated CHANGELOG.md with comprehensive details about the new version management features including automated version bumping, pyproject.toml as single source of truth, Make targets, and complete documentation.
Explicitly document that all changes must be committed before creating a pull request. Updated workflow steps to: - Add dedicated step 3: 'Ensure all changes are committed' - Clarify git status must show 'nothing to commit, working tree clean' - Add requirement to Common PR Checks section - Renumber subsequent steps accordingly This makes the requirement impossible to miss and aligns with the detailed commit workflow in git-commit.md.
Add two new commands for comprehensive GitHub issue resolution: 1. solve-issue.md - Methodical approach with user feedback: - Fetches and analyzes GitHub issues - Enforces clean working directory requirement - Creates issue-numbered branches (issue<N>) - Generates implementation plans with multiple options - Saves plans to .cursor/plans/issue-<N>.md - Presents pros/cons for user decision-making - Makes regular atomic commits throughout - Enforces SOLID, DRY, and no-hardcoding principles - Creates draft PR with comprehensive documentation 2. yolo-issue.md - Autonomous YOLO mode: - Fully autonomous with minimal user intervention - Makes independent architectural decisions - Enforces production-ready quality standards - Comprehensive testing (>90% coverage requirement) - Auto-runs linters and fixes issues - Creates detailed internal implementation plans - Makes highly organized atomic commits - Generates production-ready PRs with metrics Both commands: - Reference existing git-commit.md and create-pr.md guidelines - Enforce clean working directory before starting - Never skip pre-commit hooks - Follow conventional commit format - Create proper issue-linked PRs - Include quality checklists and best practices Usage: /solve-issue <number> - for methodical approach /yolo-issue <number> - for autonomous mode
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Overview
Implements automated version management system with pyproject.toml as single source of truth for version numbers.
✨ Features
Scripts
scripts/get_version.py: Extract version from pyproject.tomlscripts/bump_version.py: Automated semantic version bumpingMakefile Targets
make version: Display current versionmake bump-patch: Bump patch version (0.3.2 → 0.3.3)make bump-minor: Bump minor version (0.3.2 → 0.4.0)make bump-major: Bump major version (0.3.2 → 1.0.0)Documentation
docs/VERSION_MANAGEMENT.md: Comprehensive guide covering:🎁 Benefits
🧪 Testing
📝 Changes
pyproject.tomlto v0.3.3📦 Release Notes
See CHANGELOG.md for detailed release notes.
✅ Ready to Merge
All tests passing ✓
Documentation complete ✓
Scripts tested and working ✓