cv4pve-pepper 2.0.1

What's new in 2.0.1

Documentation
- Documentation site. The documentation moved from the README to corsinvest.github.io/cv4pve-pepper: getting started, permissions, options, SPICE and VNC, desktop shortcut and troubleshooting, each checked against the code and on a test cluster, including which viewer to use, also for VNC (#43). The README is now a short overview
Fixed
- --debug and --log-level now control all diagnostic output the same way: pepper's own lines (viewer command, VNC bridge, start/resume) go through the logger instead of the console, so --log-level shows them too
- Secrets are masked in diagnostic output: the VNC ticket in the WebSocket URL and the SPICE password
- --dry-run no longer leaves a .vv file with a valid ticket in the temp folder
- Errors are reported as ERROR: … like the other cv4pve tools, with the stack trace when --debug is set
- --start-or-resume stops with the real reason when the start or resume fails, instead of trying to open the console of a stopped VM; the result of the start task is checked
- Windows release builds are now WinExe, as intended in 2.0.0: no console window when launched from a shortcut (the release is built on Linux, so the output type now follows the target runtime)
- --proxy help and README: the SPICE proxy is an IP address or host name reached on port 3128, not a URL
- Packaging license was MIT; the project is GPL-3.0-only
Changed
- Updated Corsinvest.ProxmoxVE.Api.Console to 9.2.3
- Product icon (Lucide monitor-play) and Windows executable icon
- Project metadata, symbols and Source Link aligned with the other cv4pve tools
What's Changed
- ci: use shared cv4pve-tools CI workflow and declare publish permissions by @franklupo in #44
- Fix diagnostic output and error handling, align project with cv4pve tools by @franklupo in #45
- Documentation site by @franklupo in #46
- Release 2.0.1 by @franklupo in #47
Full Changelog: v2.0.0...v2.0.1

Full release notes »