Skip to content

Release v0.2.7: Complete CLI Reliability & Package Integrity

Choose a tag to compare

View all tags
@freshtechbro freshtechbro released this 14 Aug 19:22
· 20 commits to master since this release
v0.2.7
3ff6f71
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

🔧 Complete CLI Bug Resolution & Package Integrity

Version 0.2.7 represents the final resolution of all CLI-related issues, ensuring complete reliability and package integrity for all users.

🎯 Critical Fixes Summary

✅ CLI Onboarding Loop Bug (v0.2.5)

  • Fixed persistent first-run detection issues where vibe command repeatedly triggered setup wizard
  • Context-aware configuration system using enhanced TransportContext pattern for CLI vs Server differentiation
  • Smart project root detection using process.cwd() instead of package directory
  • Dual-location configuration saving (user directory + package fallback) for maximum reliability

✅ Runtime Dependency Issues (v0.2.6)

  • Fixed "Cannot find package '@xenova/transformers'" errors by moving dependency to correct location
  • Resolved CLI startup failures related to missing runtime dependencies
  • Enhanced semantic matching functionality with proper dependency management
  • Improved npm package reliability for global installations

✅ Missing Configuration Files (v0.2.7)

  • Fixed "Failed to read file" errors by including all configuration files in npm package
  • Added llm_config.json and job-timeout-config.json to package files array
  • Ensured complete package functionality out of the box
  • Enhanced package integrity for production deployments

🚀 Enhanced User Experience

Smart Auto-Detection

  • Intelligent project root detection from current working directory
  • Context-aware first-run detection with transport-specific validation
  • Multi-directory support - run vibe from any directory in your project
  • Proper configuration isolation between different projects

Robust File Management

  • Enhanced error handling for configuration persistence and loading
  • Better validation of configuration file locations and accessibility
  • Comprehensive fallback mechanisms for maximum reliability
  • Improved setup wizard with better user feedback

🧪 Quality Assurance & Testing

Comprehensive Validation

  • Local package testing before each release to prevent runtime issues
  • Extensive CLI onboarding flow testing covering all edge cases
  • Enhanced error messages and debugging information throughout
  • Security audits pass with zero vulnerabilities

Production Ready

  • TypeScript compilation with strict typing enforcement (zero errors)
  • ESLint validation passes with no issues
  • Full build verification before each release
  • Backward compatibility maintained for all existing setups

📦 Installation & Upgrade

# Install latest stable version
npm install -g vibe-coder-mcp@0.2.7

# Or update existing installation
npm update -g vibe-coder-mcp

# Verify installation
vibe --help

🔍 What's Fixed

Before v0.2.7:

  • CLI repeatedly asked for setup even after configuration
  • Runtime errors for missing dependencies
  • Configuration loading failures
  • Inconsistent behavior between directories

After v0.2.7:

  • ✅ CLI properly detects existing configuration
  • ✅ All dependencies included and accessible
  • ✅ Configuration files load correctly
  • ✅ Consistent behavior from any project directory

🎉 User Benefits

  • Zero Configuration Hassle: CLI works immediately after first setup
  • Reliable Functionality: All features work out of the box
  • Cross-Directory Support: Use from any location in your project
  • Production Ready: Thoroughly tested and validated
  • Complete Package: No missing files or dependencies

🔗 Links & Resources

Full Changelog: v0.2.6...v0.2.7

This release completes the CLI reliability initiative and ensures all users have a seamless, production-ready experience with vibe-coder-mcp.

Assets 2
Loading