Repository navigation
Release 1.6.1: repair selected updater stop and upgrade compatibility - #26
Merged
Merged
Conversation
added 2 commits
November 4, 2026 10:03
Allow bounded stop acknowledgement headroom without changing graceful-stop time or other request deadlines, and retain safe primary/recovery diagnostics. Recognize the exact pinned released 1.5.4 standard configuration so the matching host CLI can preserve guarded upgrades to the repaired proxy.
Keep the release limited to the reviewed stop-response, diagnostics and released-configuration compatibility repair. Record the peeled provenance commit and leave unreleased Fleet work on 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
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.
Release 1.6.1 fixes selected updates that can roll back after a slow Docker stop acknowledgement. It preserves the shutdown grace, bounds the response wait, and records safe failure/recovery details. The matching host CLI can recognize the exact pinned 1.5.4 configuration while retaining authentication and drift checks.
This is the approved main-based backport of #25. Merge after #25; unrelated unreleased Fleet changes remain on dev.
Validation: