feat(rust): manage Linux Spotify updates from the client - #3953
Merged
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
Managed Linux Spotify installations can now update from inside the client, with progress and recovery owned by the daemon. The same transaction keeps terminal and desktop launches on the selected installation.
This completes the client integration for the Linux installer. Updates use Spotify's official package feed and require an exact verified classmap. The candidate is patched before activation; a failed activation restores the previous configuration and launchers. Reinstall keeps the selected channel, and the daemon follows changes to the installation directory.
Native updater protection remains a separate fact. An unknown block state is omitted from the manifest instead of being reported as unblocked. A version probe no longer counts as a running Spotify client during launch verification.
The workspace version advances to
3.0.0-beta.18. Abrupt daemon termination is reported as an interrupted job with a reinstall command; automatic rollback covers normal activation failures.Related: #3950
Validation