daf release command fails with pyproject.toml - expects setup.py version field

[itdove]

Steps to Reproduce

1. Run daf release 2.1.0 --dry-run
2. Observe error: "Could not find version in setup.py"

Actual Behavior

The daf release command fails when the project uses pyproject.toml for package configuration instead of setup.py. The command tries to parse version from setup.py which only contains setup() with no version parameter.

Expected Behavior

The daf release command should support both setup.py and pyproject.toml formats. It should:

• First check if version exists in pyproject.toml under [project] section
• Fall back to setup.py if pyproject.toml doesn't exist
• Support updating version in both files during release process

Additional Context

DevAIFlow migrated to pyproject.toml in an earlier version but the release automation wasn't updated. Manual release process from RELEASING.md works but requires manual version updates in both:

• devflow/init.py
• pyproject.toml

Workaround

Use manual release process from RELEASING.md until fixed.

[itdove]

✅ Session Complete

Project: devaiflow
Goal: #360: daf release command fails with pyproject.toml - expects setup.py version field
Time Spent:
0h 13m total

• dvernier: 0h 10m
• unknown: 0h 2m
  Branch: 360

Perfect! The fix is complete and working. Let me create a summary of the changes:

Summary

I've successfully fixed issue #360: daf release command fails with pyproject.toml - expects setup.py version field.

Changes Made

1. Updated ReleaseManager class (devflow/release/manager.py):

   • Modified __init__() to reference pyproject.toml
   • Updated read_current_version() to:
     • Check pyproject.toml first (modern PEP 517/518/621 format)
     • Fall back to setup.py for backward compatibility
     • Raise appropriate errors if neither file has version info
   • Updated update_version_files() to:
     • Update pyproject.toml when it exists
     • Skip setup.py if it doesn't contain a version field (modern format)
     • Maintain backward compatibility with projects still using setup.py
   • Updated validate_release_prepared() and prepare_release() to show correct file names in error messages

2. Updated release_command.py (devflow/cli/commands/release_command.py):

   • Modified display messages to show correct package file (pyproject.toml vs setup.py)
   • Updated commit messages to reference the correct file being updated

3. Added comprehensive tests (tests/test_release_manager_pyproject.py):

   • 8 new tests covering:
     • Reading version from pyproject.toml
     • Reading dev versions from pyproject.toml
     • Updating version in pyproject.toml
     • Backward compatibility with setup.py
     • Error handling for missing or invalid configurations
     • Skipping empty setup.py files during updates

4. Updated OpenWolf tracking files:

   • Added entry to .wolf/buglog.json documenting the bug fix

Test Results

• ✅ All 3654 existing tests pass
• ✅ All 8 new pyproject.toml tests pass
• ✅ Backward compatibility maintained for projects using setup.py
• ✅ Manual verification: daf release 2.2.0 --dry-run works correctly

How It Works

The fix implements a smart detection strategy:

1. If pyproject.toml exists → read/write version there
2. If only setup.py exists with version field → use it (backward compatibility)
3. If neither has version info → raise helpful error

This ensures the release command works for:

• Modern Python projects using pyproject.toml (like DevAIFlow)
• Legacy projects still using setup.py
• Mixed configurations during migration periods

The fix resolves the issue completely while maintaining full backward compatibility! 🎉

Generated by DevAIFlow

[itdove]

✅ Session Complete

Project: devaiflow
Goal: #360: daf release command fails with pyproject.toml - expects setup.py version field
Time Spent:
0h 27m total

• dvernier: 0h 26m
• unknown: 0h 1m
  Branch:

The session created 1 new files and modified 3 existing files. Work included: made 10 edits, wrote 1 files, ran 21 commands.

Generated by DevAIFlow

[itdove]

✅ Session Complete

Project: devaiflow
Goal: #360: daf release command fails with pyproject.toml - expects setup.py version field
Time Spent:
0h 36m total

• dvernier: 0h 35m
• unknown: 0h 1m
  Branch:

Perfect! I've successfully created a draft pull request for the bug fix:

PR Created: #365

URL: #365

Summary of Work Completed

✅ Bug Fix Implemented

• Fixed daf release command to support pyproject.toml
• Maintains full backward compatibility with setup.py-only projects
• Smart detection: checks pyproject.toml first, falls back to setup.py

✅ Code Changes

• devflow/release/manager.py: Added pyproject.toml support
• devflow/cli/commands/release_command.py: Updated display messages
• tests/test_release_manager_pyproject.py: 8 new comprehensive tests

✅ Testing

• All 8 new tests pass
• All 3,654 existing tests pass (zero regressions)
• Manual verification: daf release 2.2.0 --dry-run works correctly

✅ Commits

1. 2e50786 - fix(release): support pyproject.toml for version management (daf release command fails with pyproject.toml - expects setup.py version field #360)
2. 8a269ae - chore: add OpenWolf context management setup

The PR is in draft mode and ready for review. The uncommitted changes shown are OpenWolf session tracking files (.wolf/ directory) which are not part of the fix.

Generated by DevAIFlow