Release Server 2.2.0 with online payload backup coordination - #126
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
2 participants
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.
Prepare the next additive minor release for #124 / #125. The operator-only reclamation hold, bounded expiry, database-process tests and snapshot ordering documentation are already merged and feature-qualified.
Update the single source-release record to Server 2.2.0 and independently advance the chart to 0.1.77, then render the existing bounded consumer set. No SDK/Workflow dependency or protocol window changes; historical versions/tags remain untouched.
Before tagging: repository checks must pass for this exact source. The existing protected Release workflow then owns multi-architecture Docker Hub/GHCR publication, image provenance, first-run/Compose checks, protocol catalog validation and rolling-tag promotion. Verify the published operator command and actual database/payload recovery with the immutable image before a downstream backup rollout. This PR is not evidence that a downstream backup implementation is ready.