Add community standards files#11
Merged
Merged
Conversation
Syncthing self-upgraded to v2.0.16 on existing installs before the --no-upgrade flag was added, writing a config.xml in format v52 that the old pinned v1.27.10 binary cannot read. ensure_binary() then downgrades the on-disk binary back to v1.27.10 on every launch, and Syncthing fails to boot with "config file version (52) is newer than supported version (37)", putting the app into an endless retry loop. Align the pin with the config format already on disk. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Notes
Rebased onto main; core code files match main exactly.