v0.4.2

Full Changelog: v0.4.1...v0.4.2

v0.4.1: chore: bump version to 0.4.1

🎯 What's Changed

📝 Project Rename

• Renamed project from "AutoDev GitHub Agent Action" to "AutoDev Remote Agent"
• Updated all documentation files to reflect the new name
• Maintained backward compatibility for CLI commands and repository URLs

📚 Updated Documentation

• ✅ README.md - Updated main title
• ✅ action.yml - Updated GitHub Action name field
• ✅ MARKETPLACE.md - Updated marketplace title
• ✅ QUICK_START.md - Updated quick start guide title
• ✅ CONFIGURATION.md - Updated configuration guide
• ✅ package.json - Updated description
• ✅ PUBLISHING_GUIDE.md - Updated publishing guide
• ✅ Source code comments and descriptions

🔄 Backward Compatibility

• Repository URL remains: unit-mesh/autodev-remote-agent-action
• CLI command name unchanged: autodev-github-action
• All existing workflows continue to work without changes

🚀 Usage

- name: Analyze Issue
  uses: unit-mesh/[email protected]
  with:
    github-token: ${{ secrets.GITHUB_TOKEN }}
    deepseek-token: ${{ secrets.DEEPSEEK_TOKEN }}
    analysis-depth: medium
    auto-comment: true
    auto-label: true

v0.4.0 - Analysis Transparency & Smart File Filtering

🔍 Analysis Transparency & Smart File Filtering

This major release introduces comprehensive analysis transparency features and intelligent file filtering capabilities, making it easier to understand and optimize issue analysis results.

🌟 New Features

🔍 Analysis Process Transparency

• Process Visibility: See exactly what files were scanned, analyzed, and filtered
• Step-by-Step Tracking: Detailed breakdown of each analysis phase with timing
• LLM Call Monitoring: Track AI service interactions and errors
• Smart Diagnostics: Get specific explanations when analysis results are limited

🛠️ Intelligent File Filtering

• Configurable File Inclusion: Control which file types are included in analysis
• Pattern-Based Filtering: Use glob patterns to include/exclude specific files
• Force Include: Always include critical files regardless of AI filtering
• Smart Detection: Automatically identify important files that were filtered

💡 Improved User Experience

• Actionable Suggestions: Get specific tips for improving issue descriptions
• Filter Explanations: Understand why certain files were excluded
• Better Error Messages: Clear explanations when analysis fails
• Performance Insights: See analysis timing and optimization suggestions

⚙️ New Configuration Options

- uses: unit-mesh/[email protected]
  with:
    # File filtering controls
    include-config-files: true    # Include jest.config.js, rollup.config.mjs, etc.
    include-test-files: true      # Include __tests__/, *.test.js, etc.
    include-patterns: "*.config.js,*.config.ts,docker-compose.yml"
    exclude-patterns: "*.min.js,*.bundle.js"
    force-include-files: "important-config.js,critical-setup.ts"

📊 Enhanced Analysis Comments

Analysis comments now include:

• Process Summary: Files scanned vs. analyzed vs. filtered counts
• Filtered Files Section: Specific files excluded with reasons
• Improvement Suggestions: How to get better analysis results
• Diagnostic Information: Troubleshooting tips for limited results

🔧 What's Changed

Core Improvements

• Added AnalysisProcessInfo type for comprehensive process tracking
• Implemented file scanning and categorization (config, test, source files)
• Enhanced error handling with detailed diagnostic information
• Added LLM call tracking and failure analysis

New Files

• CONFIGURATION.md - Complete configuration guide
• TRANSPARENCY.md - Understanding analysis transparency
• examples/advanced-workflow.yml - Advanced usage examples
• scripts/test-transparency.js - Testing transparency features

Documentation Updates

• Updated README with new configuration options
• Enhanced MARKETPLACE.md with transparency features
• Added comprehensive configuration examples
• Improved troubleshooting guides

🚀 Migration Guide

This release is backward compatible. Existing configurations will continue to work without changes.

To Enable New Features:

1. Update your workflow to use @v0.4.0
2. Optionally add file filtering configuration
3. Review analysis comments for new transparency information

Recommended Updates:

# Before
- uses: unit-mesh/[email protected]

# After
- uses: unit-mesh/[email protected]
  with:
    include-config-files: true
    include-test-files: true

🐛 Bug Fixes

• Fixed aggressive file filtering that excluded important configuration files
• Improved error handling when LLM services are unavailable
• Enhanced comment generation fallback mechanisms
• Better handling of empty or insufficient analysis results

📈 Performance Improvements

• Optimized file scanning with better pattern matching
• Reduced unnecessary LLM calls through smarter caching
• Improved analysis step timing and reporting
• Better memory usage for large repositories

🔗 Useful Links

• Configuration Guide
• Transparency Documentation
• Advanced Examples
• Issue Tracker

🙏 Acknowledgments

Thanks to all users who provided feedback on file filtering issues and requested better transparency in the analysis process. This release directly addresses those concerns.

---

Full Changelog: v0.3.8...v0.4.0

v0.3.8

Full Changelog: v0.3.7...v0.3.8

v0.3.7

Full Changelog: v0.3.6...v0.3.7

v0.3.6

Full Changelog: v0.3.5...v0.3.6

v0.3.5

Full Changelog: v0.3.4...v0.3.5

v0.3.4

Full Changelog: v0.3.3...v0.3.4

release: bump version to v0.3.1

- Update version in package.json and all documentation
- Fix bundling issue for GitHub Actions compatibility
- All dependencies now properly bundled in dist files

release: prepare v0.3.0 with self-testing workflows

- Bump version to 0.3.0 in package.json and all documentation
- Add GitHub workflows to use our own action for issue analysis
- Create issue templates for better testing
- Add manual test workflow for specific issue analysis
- Update release preparation script
- Ready for dogfooding - using our own action to analyze issues