Skip to content

feat(rust): manage Linux Spotify updates from the client - #3953

Merged
afonsojramos merged 1 commit into
v3-betafrom
fix/unknown-update-protection
Sep 17, 2026
Merged

afonsojramos merged 1 commit into
v3-betafrom
fix/unknown-update-protection

Conversation

@afonsojramos

Copy link
Copy Markdown
Member

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

  • Live Manager-driven upgrade from a retained Spotify 1.2.84 fixture to the official 1.2.96 package; patched first boot and both launchers verified.
  • Injected candidate launch failure: readable progress, failed job, restored configuration and launchers, previous client restarted.
  • Duplicate admission joined the running job; unauthenticated requests, shutdown during update, and competing CLI operations were rejected.
  • After integrating current upstream fixes: 166 Rust tests passed, 3 ignored; Clippy and payload tests passed.

@coderabbitai

coderabbitai Bot commented Sep 17, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 4b714bc5-b89e-4c8e-9196-29d283526c73

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@afonsojramos
afonsojramos merged commit 64ecd93 into v3-beta Sep 17, 2026
5 checks passed
@afonsojramos
afonsojramos deleted the fix/unknown-update-protection branch September 17, 2026 00:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant