Repository navigation
Version 0.6.0 - #87
Merged
Merged
Conversation
The docs say which versions used the old per-user folder, for people who come from the 0.5.2 release rather than from a beta. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
Cargo.tomlfiles andCargo.lock. The tagv0.6.0publishes it as a release, the first since 0.5.2.docs/how-it-works.md: "Until 0.6.0-beta.6" now reads "Until 0.6.0 (0.6.0-beta.6 on the beta channel)". Someone on 0.5.2 never saw beta.6.The update from 0.5.2
The 0.5.2 app checks
releases/latest, sees 0.6.0 and runs the setup with/SILENT /NORESTARTthrough a plainCommand::spawn, without administrator rights. Checked against the code and the beta.7 setup:camless-setup.exe(Inno Setup 6.7.0) saysrequestedExecutionLevel level="asInvoker". Inno then asks UAC on its own forPrivilegesRequired=admin. So the old app starts it without error 740.installer/camless.issandgui/src/update.rsare the same in v0.5.2 and v0.6.0-beta.6. Security: install in Program Files on Windows, guard the administrator task and the service's files #84 tested the move from a beta.6 install, so it covers a 0.5.2 install too:%LOCALAPPDATA%\Programs\camless, and the dir page was off in 0.5.2, so nobody picked another folder.POST /v1/stop, and 0.5.2's own setup already stopped it that way.camless (<user>)withGetUserNameW, the same nameTaskNamebuilds fromGetUserNameString, soRenewTaskfinds it and writes it again.camless.tomlin%APPDATA%\camless(no config changes since 0.5.2), the WebView2 profile in%LOCALAPPDATA%\camless\WebView2, Start with Windows (autostart::follow), the history (state::bring_history_over), and a PawnIO module next to the old exe (CopyModule).install.shis unchanged since 0.5.2, so the update works as before.Release notes
--generate-noteslists the PRs since v0.5.2. Once the release is out, put this above them withgh release edit v0.6.0:Upgrading from 0.5.2, and what's new
Upgrading from 0.5.2
Windows. camless now installs in
C:\Program Files\camless, and its setup asks for administrator rights.camless-setup.exemay make changes. It names an unknown publisher, because camless is not code-signed. Answer Yes. If you answer No, nothing changes: open camless again and update later.%LOCALAPPDATA%\Programs\camless: the exes, the shortcuts, the entry in Settings → Apps, and a PawnIO module you put there. Settings and profiles in%APPDATA%\camlessstay. Start with Windows and Start as administrator without asking point at the new folder. The service brings the history along the first time it runs as administrator.C:\Program Files\camless\camless.exe.camless.tomlbeside the oldcamless.exe, it stays in the old folder. Move it, with itsprofilesfolder, to%APPDATA%\camless.Linux. Nothing changes. Update works as before.
What's new since 0.5.2
Testing
cargo test --workspace --release --lockedon Linux (Ubuntu container): 180, 37 and 25 tests pass.The beta.7 setup was downloaded from the release, its SHA-256 checked, and its manifest read.
The update from 0.5.2 on a Windows 11 PC (Ryzen 7 5800X3D, RTX 4070 SUPER, Kraken Elite 2024 with its LCD on a web page):
unins000.exe /VERYSILENT. Both exes, the uninstaller, the PawnIO module, the task, Start with Windows, the shortcuts and the entry in Settings → Apps were gone, anddatastayed./MERGETASKS=desktopicon.AMDFamily17.binwent into%LOCALAPPDATA%\Programs\camless. In the 0.5.2 app: Start with Windows and Start as administrator without asking turned on, the service restarted through the task, CPU temperature on, the beta channel offering 0.6.0-beta.7.C:\Program Files\camless.camless (<user>)and Start with Windows pointing at Program Files, the Start menu and desktop shortcuts for all users. The app ran without administrator rights and the service with them, started through the renewed task. CPU temperature read 52.5 °C, the history went on inC:\Program Files\camless\data\history, and the LCD's Edge ran with--remote-debugging-pipeas a child of Explorer.ConsentPromptBehaviorAdmin=0) for the test, since nobody was at the PC to click it, and set back to 5 afterwards. So the click on the prompt itself is the one step that did not run.Not tested: a standard account, Chrome for the LCD, the uninstaller from Settings → Apps with its question about settings.
Claude Opus 5.5 on behalf of kleju13
🤖 Generated with Claude Code