docs: explain uncached compatibility refreshes - #238
Merged
Merged
Conversation
Deploying spicetify-docs with
|
| Latest commit: |
f13ddb2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://517d393a.spicetify-docs.pages.dev |
| Branch Preview URL: | https://docs-apply-no-cache.spicetify-docs.pages.dev |
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
1 participant
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.
Users whose client still misses a published compatibility fix get a documented recovery command,
spicetify apply --no-cache, with clear network requirements, failure behavior, and a return-to-Spotify check. The command reference and FAQ distinguish compatibility refreshes from theme/module updates and Spotify's music cache.Companion to spicetify/cli#3947. Keep this draft until the CLI option ships. The instructions check availability through
apply --helpand provide a normal-Apply fallback for older binaries.Validation: the documentation site built successfully, and the generated command example and FAQ link were checked. The documented success, unavailable-network failure, and developer-override conflict were exercised with the companion CLI build.