Is there a technical reason syncthing-macos is not keeping up with syncthing releases (e.g. 2.0)?
I haven't looked at the code to see whats involved, but is there any effort to keep syncthing-macos up to date with changes in syncthing versions? Will a 1.3 macos version continue to work when all of my other machines (linux, windows) are at 2.0 and beyond?
https://github.com/syncthing/syncthing-macos/releases/tag/v2.0.3%2B1
Appreciate all the work that’s happening here but the current released version of syncthings is 2.10 which is a regular release not a pre release. If this project going to continue to track releases?
I also appreciate the work that is being done here, but was also wondering about this! Another way to run the most recent version of Syncthing on macOS (v2.0.10) is to install the regular Syncthing binary via Homebrew:
brew install syncthing
And then start it as a service which will also run after reboot (probably best to quit the Syncthing version that is running in the system tray first):
brew services start syncthing
This doesn't have the tray icon like the macOS version in this repo but you can still reach the configuration page by going to http://localhost:8384 in the browser. I didn't have to configure anything, it seems to take over the configuration of the other version. Except for the missing tray icon this seems to function exactly the same, but with the added benefit of running the latest Syncthing version. Just be sure to run brew update && brew upgrade regularly to keep it up to date.
The project is not dead, don't worry I will catch up when time permits. This macOS wrapper is a one mans job unfundend only on donation base. Also v2 Syncthing still needs some flight hours. No pressure. Syncthing v1 is very stable and production ready.
See also discussion with main developer(s) on the forum @ https://forum.syncthing.net/t/roadmap-and-deprecation-of-v1-release-branch/24918/4
@basalphenaar the Syncthing project and Syncthing for macOS is not responsible or involved in the choices homebrew makes. Please use appropiate channels to report issues when there is something wrong with this "port".