v1.4.0-rc.5

This is a release candidate for the v1.4.0 minor release.

Important changes:

- A new config option maxConcurrentIncomingRequestKiB has been added to
  limit the maximum amount of request data being concurrently processed due
  to incoming requests. This limits Syncthing's peak RAM usage when there
  are many connected devices all requesting file data. The default is 256
  MiB.

- The config option maxConcurrentScans has been removed and replaced a new
  config option maxFolderConcurrency. In addition to just limiting
  concurrent scans it now also limits concurrent sync operations. The
  default is the number of available CPU threads ("GOMAXPROCS").

- Syncthing now always runs the monitor process, which previously was
  disabled with -no-restart. This facilitates crash reporting and makes
  logging behave more consistently. The observed behavior with -no-restart
  should be the same as before but the internals differ.

- The database schema has been improved and will result in a migration plus
  compaction at first startup after the upgrade.

Bugfixes:

 - syncthing#4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux)
 - syncthing#5952: panic: Should never get a deleted file as needed when we don't have it
 - syncthing#6281: Progress emitter uses 100% CPU
 - syncthing#6289: "general SOCKS server failure" since syncthing 1.3.3
 - syncthing#6300: lib/ignore: panic: runtime error: index out of range [0] with length 0
 - syncthing#6335: Crash or hard shutdown can case database inconsistency, out of sync

Enhancements:

 - syncthing#5786: Consider always running the monitor process
 - syncthing#5898: Database performance: reduce duplication
 - syncthing#5914: Limit folder concurrency to improve performance
 - syncthing#6302: Avoid thundering herd issue by global request limiter

v1.4.0-rc.4

This is a release candidate for the v1.4.0 minor release.

Important changes:

- A new config option maxConcurrentIncomingRequestKiB has been added to
  limit the maximum amount of request data being concurrently processed due
  to incoming requests. This limits Syncthing's peak RAM usage when there
  are many connected devices all requesting file data. The default is 256
  MiB.

- The config option maxConcurrentScans has been removed and replaced a new
  config option maxFolderConcurrency. In addition to just limiting
  concurrent scans it now also limits concurrent sync operations. The
  default is the number of available CPU threads ("GOMAXPROCS").

- Syncthing now always runs the monitor process, which previously was
  disabled with -no-restart. This facilitates crash reporting and makes
  logging behave more consistently. The observed behavior with -no-restart
  should be the same as before but the internals differ.

- The database schema has been improved and will result in a migration plus
  compaction at first startup after the upgrade.

Bugfixes:

 - syncthing#4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux)
 - syncthing#5952: panic: Should never get a deleted file as needed when we don't have it
 - syncthing#6281: Progress emitter uses 100% CPU
 - syncthing#6289: "general SOCKS server failure" since syncthing 1.3.3
 - syncthing#6300: lib/ignore: panic: runtime error: index out of range [0] with length 0
 - syncthing#6335: Crash or hard shutdown can case database inconsistency, out of sync

Enhancements:

 - syncthing#5786: Consider always running the monitor process
 - syncthing#5898: Database performance: reduce duplication
 - syncthing#5914: Limit folder concurrency to improve performance
 - syncthing#6302: Avoid thundering herd issue by global request limiter

v1.4.0-rc.3

This is a release candidate for the v1.4.0 minor release.

Bugfixes:

 - syncthing#4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux)
 - syncthing#5952: panic: Should never get a deleted file as needed when we don't have it
 - syncthing#6281: Progress emitter uses 100% CPU
 - syncthing#6289: "general SOCKS server failure" since syncthing 1.3.3
 - syncthing#6300: lib/ignore: panic: runtime error: index out of range [0] with length 0

Enhancements:

 - syncthing#5786: Consider always running the monitor process
 - syncthing#5898: Database performance: reduce duplication
 - syncthing#5914: Limit folder concurrency to improve performance
 - syncthing#6302: Avoid thundering herd issue by global request limiter

Important changes:

- A new config option maxConcurrentIncomingRequestKiB has been added to
  limit the maximum amount of request data being concurrently processed due
  to incoming requests. This limits Syncthing's peak RAM usage when there
  are many connected devices all requesting file data. The default is 256
  MiB.

- The config option maxConcurrentScans has been removed and replaced a new
  config option maxFolderConcurrency. In addition to just limiting
  concurrent scans it now also limits concurrent sync operations. The
  default is the number of available CPU threads ("GOMAXPROCS").

- Syncthing now always runs the monitor process, which previously was
  disabled with -no-restart. This facilitates crash reporting and makes
  logging behave more consistently. The observed behavior with -no-restart
  should be the same as before but the internals differ.

- The database schema has been improved and will result in a migration plus
  compaction at first startup after the upgrade.

v1.4.0-rc.2

This is a release candidate for the v1.4.0 minor release.

Bugfixes:

 - syncthing#4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux)
 - syncthing#5952: panic: Should never get a deleted file as needed when we don't have it
 - syncthing#6281: Progress emitter uses 100% CPU
 - syncthing#6289: "general SOCKS server failure" since syncthing 1.3.3
 - syncthing#6300: lib/ignore: panic: runtime error: index out of range [0] with length 0

Enhancements:

 - syncthing#5786: Consider always running the monitor process
 - syncthing#5898: Database performance: reduce duplication
 - syncthing#5914: Limit folder concurrency to improve performance
 - syncthing#6302: Avoid thundering herd issue by global request limiter

Important changes:

- A new config option maxConcurrentIncomingRequestKiB has been added to
  limit the maximum amount of request data being concurrently processed due
  to incoming requests. This limits Syncthing's peak RAM usage when there
  are many connected devices all requesting file data. The default is 256
  MiB.

- The config option maxConcurrentScans has been removed and replaced a new
  config option maxFolderConcurrency. In addition to just limiting
  concurrent scans it now also limits concurrent sync operations. The
  default is the number of available CPU threads ("GOMAXPROCS").

- Syncthing now always runs the monitor process, which previously was
  disabled with -no-restart. This facilitates crash reporting and makes
  logging behave more consistently. The observed behavior with -no-restart
  should be the same as before but the internals differ.

- The database schema has been improved and will result in a migration plus
  compaction at first startup after the upgrade.

v1.4.0-rc.1

This is a release candidate for the v1.4.0 minor release.

Bugfixes:

 - syncthing#4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux)
 - syncthing#5952: panic: Should never get a deleted file as needed when we don't have it
 - syncthing#6281: Progress emitter uses 100% CPU
 - syncthing#6289: "general SOCKS server failure" since syncthing 1.3.3
 - syncthing#6300: lib/ignore: panic: runtime error: index out of range [0] with length 0

Enhancements:

 - syncthing#5786: Consider always running the monitor process
 - syncthing#5898: Database performance: reduce duplication
 - syncthing#5914: Limit folder concurrency to improve performance
 - syncthing#6302: Avoid thundering herd issue by global request limiter

Important changes:

- A new config option maxConcurrentIncomingRequestKiB has been added to
  limit the maximum amount of request data being concurrently processed due
  to incoming requests. This limits Syncthing's peak RAM usage when there
  are many connected devices all requesting file data. The default is 256
  MiB.

- The config option maxConcurrentScans has been removed and replaced a new
  config option maxFolderConcurrency. In addition to just limiting
  concurrent scans it now also limits concurrent sync operations. The
  default is the number of available CPU threads ("GOMAXPROCS").

- Syncthing now always runs the monitor process, which previously was
  disabled with -no-restart. This facilitates crash reporting and makes
  logging behave more consistently. The observed behavior with -no-restart
  should be the same as before but the internals differ.

- The database schema has been improved and will result in a migration plus
  compaction at first startup after the upgrade.

v1.3.4

This is a regularly scheduled patch release.

Bugfixes:

 - syncthing#4570: Negative percentage and data to sync
 - syncthing#5867: Progress bar not visible
 - syncthing#6044: Clicking "Save" in options says "You have unsaved changes" when changing automatic upgrade setting
 - syncthing#6213: Tone down STUN logging a bit
 - syncthing#6222: Connection Error on Listing More Locally Changed Files
 - syncthing#6234: Docker image uses wrong path for default folder
 - syncthing#6240: GUI: ignore patterns path is one row too low
 - syncthing#6263: Panics due to database being closed

v1.3.4-rc.1

This is a release candidate for the v1.3.4 patch release.

Bugfixes:

 - syncthing#4570: Negative percentage and data to sync
 - syncthing#5867: Progress bar not visible
 - syncthing#6044: Clicking "Save" in options says "You have unsaved changes" when changing automatic upgrade setting
 - syncthing#6213: Tone down STUN logging a bit
 - syncthing#6222: Connection Error on Listing More Locally Changed Files
 - syncthing#6234: Docker image uses wrong path for default folder
 - syncthing#6240: GUI: ignore patterns path is one row too low
 - syncthing#6263: Panics due to database being closed

v1.3.3

This is a release candidate for the v1.3.3 patch release.

Bugfixes

 - syncthing#6104: Windows: Syncthing log file filling up primary drive.
 - syncthing#6133: Race condition in restarting folder
 - syncthing#6139: Some sync errors get cleared despite them still being valid
 - syncthing#6206: Soft limit for maxfiles is NOT increased to the hard one on macOS

Enhancements

 - syncthing#5887: Upgrade Button Does Not Have Confirmation Dialog
 - syncthing#6057: "Nearby devices" links should look more like links (mouse pointer)
 - syncthing#6190: Do not create .stignore if there are no ignore patterns

v1.3.3-rc.1

This is a release candidate for the v1.3.3 patch release.

Bugfixes

 - syncthing#6104: Windows: Syncthing log file filling up primary drive.
 - syncthing#6133: Race condition in restarting folder
 - syncthing#6139: Some sync errors get cleared despite them still being valid
 - syncthing#6206: Soft limit for maxfiles is NOT increased to the hard one on macOS

Enhancements

 - syncthing#5887: Upgrade Button Does Not Have Confirmation Dialog
 - syncthing#6057: "Nearby devices" links should look more like links (mouse pointer)
 - syncthing#6190: Do not create .stignore if there are no ignore patterns

v1.3.2

This is a regularly scheduled patch release.

Bugfixes:

 - syncthing#5810: GUI theme not changing on WebKit-based/like browsers
 - syncthing#5968: Folder "Up To Date" but has pending "Revert Local Changes"
 - syncthing#5980: (De)select all not working in add device dialog
 - syncthing#6027: Folder shows as "Syncing" when there is no data transfer
 - syncthing#6043: Cannot exit after failed startup
 - syncthing#6081: QUIC accept error loops too quickly, causing excessive log output
 - syncthing#6090: Pull-scan loop due to symlink traversal
 - syncthing#6093: cmd/stdiscosrv: Data race in replication
 - syncthing#6136: API + UI device last seen is empty/Never
 - syncthing#6160: Uses too much RAM when syncing large files (1.3.0+)

Enhancements:

 - syncthing#6036: Generate HTTPS certificates accepted by iOS 13 / macOS Catalina
 - syncthing#6056: Improve sharing tab when there are no devices to share with
 - syncthing#6115: Change Web UI based on prefers-color-scheme