chore: prepare Server 1.8.1 - #85
Merged
Merged
Conversation
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
Production behavior
Playback and provider media remain behind the Server API boundary. Profile-scoped data, recommendations and notifications follow the active account profile, while provider media handles expire independently of upstream URLs.
Deployment requirements
Publish the Server 1.8.1 image from main and pin the production server service to its immutable digest. The profile migration is additive and must run through the normal startup migration path. Preserve the existing database volume and configuration as the rollback point.
Runtime verification
Tests
Rollback
Restore the previous Server image digest and submodule revision, then recreate only the typetype-server service. Keep the additive migration data intact unless the documented rollback procedure requires database restoration.