chore: updates for v2 changes #901
Open
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
|
Would you also be able to update the build instructions at https://docs.syncthing.net/dev/building with information on requiring |
* main: (28 commits) chore(config): document options for audit logs (#916) chore(advanced): clarify multiple connections over relays (#911) fix(specs): state that both A and B are in session mode (fixes #802) (#908) build(deps): bump golang.org/x/crypto from 0.31.0 to 0.35.0 in /_script (#910) Update author list fix(config): update default value of `maxConflicts` (#929) fix(profiling): sentence clarity (#928) feat(faq): add note with example about what can be synced (#922) chore(bep): update for TLS 1.3 (#924) feat(events): add information on X-Forwarded-For header (#907) chore(config): mention STUN SRV record (#904) Update author list fix(relay): document RelayFull message (fixes #880) (#909) feat(tuning): add section for LAN-only (fixes #834) (#915) fix(faq): update location of paths tab (#917) Update author list feat(faq): add information on setting network to private in Windows (#914) chore: remove option for enabling old TLS versions on sync connections (#913) chore(contrib): add sm2 and move munin-syncthing to unmaintained (#912) Update author list ...
* main: chore(specs): update BEP regarding multiple cluster config messages (#932)
calmh
changed the title
diff --git a/users/releases.rst b/users/releases.rst
index 1690376..58db561 100644
--- a/users/releases.rst
+++ b/users/releases.rst
@@ -16,7 +16,7 @@ following criteria:
- Is the new version protocol incompatible with the previous one, so that
they cannot connect to each other or otherwise can't sync files for some
- reason? That's a new *major* version. (This hasn't happened yet.)
+ reason? That's a new *major* version.
- Are there changes in the REST API so that integrations or wrappers
need changes, or did the database schema or configuration change so that a |
|
Well the version incompatibility hasn't happened yet, but if it did it would be another major version 😅 |
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.
wip