Repository navigation
fix(fleet): adopt the released 1.6 standard configuration - #24
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.
Users upgrading a released 1.6 installation could be refused as unsupported even when its nginx configuration was stock. Adoption now recognizes that exact pinned configuration, preserves the account-link routes, auth storage and certificate paths, and continues to refuse custom configuration drift.
This composes the reviewed change with the recovery fix. The authority record is consolidated into valid JSON while preserving its content, with the existing date represented as an ISO string.
Related: #23
Validation: 203 combined integration cases passed. Auth/account/selection checks passed 148 cases plus the exact 2 Unix-IPC reruns with local IPC allowed. The current wheel matches 32 source members and 8 pinned assets; installed rendering passes for both TLS modes. Two independent composition reviews are clean. Protected CI and existing native/site acceptance remain required.