Version 0.7.0

[blacknon]

Release Highlights

This release brings a major update across the lssh suite, with new demo and test infrastructure, stronger SSH session reuse, better proxy support, and substantial improvements to lsshell, lsftp, and lscp.
Additionally, the sub-projects lsmon and lsshell have been integrated.

Added

• Added a full Docker Compose based demo environment under demo/
• Added end-to-end tests for the demo environment
• Added examples for:
  • password authentication
  • public key authentication
  • SSH proxying
  • HTTP proxying
  • SOCKS5 proxying
  • nested proxy chains
  • bastion-style access
  • local_rc based shell customization
• Added ControlMaster / ControlPersist support
• Added tunnel support with --tunnel
• Added background execution support with -f
• Added new mise tasks for demo usage and testing
• Added CI workflows for release, tests, and demo E2E verification

Improved

• Improved lsshell with process substitution support and better local command integration
• Improved lsshell completion and duplicate server handling
• Improved lsftp command set, including copy-related operations
• Improved lscp stability, including parallel copy behavior
• Improved proxy routing support, including multi-hop SSH/HTTP/SOCKS combinations
• Improved OpenSSH config handling and ControlPersist integration
• Improved Windows build compatibility across the project
• Reworked and expanded the documentation across the main README, command READMEs, and demo guide

Fixed

• Fixed several lsshell issues around outexec, server completion, and command behavior
• Fixed lscp / lsftp issues related to Windows support
• Fixed ControlPersist and proxy route handling in SSH connections
• Fixed multiple demo and CI issues discovered while adding E2E coverage
• Bugfix Lsftp not working on windows 11 #146, Lscp is not correct in Windows #105

Notes

• This release includes substantial internal refactoring across command entrypoints, configuration loading, SSH connection handling, monitor support, and vendored dependencies.
• The demo environment is now one of the easiest ways to validate real-world connection patterns locally before using them in production.