Repository navigation
Seed upgrade checks with the installed release's settings defaults - #80
Merged
Merged
Conversation
andre487
enabled auto-merge (squash)
November 12, 2026 15:58
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.
The 0.4.0 release upgrade check wrote settings with current libraries, then started the published 0.3.4 service. Current defaults serialize the TLS fingerprint as DEFAULT; 0.3.4 only accepts its older lowercase tokens, so the baseline service failed before any upgrade was attempted.
Compile the small synthetic settings fixture against the installed release's Core/Runtime libraries and verify that release can read it back. Keep the existing current-version preservation checks after upgrade. Redirect service command output and retain service logs so future failures include diagnostics.
Validation: all 8 update smoke unit tests pass, including installed-library reference isolation and error output preservation. Compiled and ran the fixture against actual 0.3.4 release DLLs locally with isolated current-user encrypted test data; save/load succeeded with fingerprint default. No local application or service installation was performed. The machine-wide upgrade scenario will run in the release workflow after this automation fix is merged; the v0.4.0 tag remains unchanged.