Please note that this release will not work (at all) on any Windows 7/Windows Server 2008. I just have tested it myself - it fatal crash right at the start even before any errors can be put to the logs.
And most likely won’t work on Windows 8 / Windows Server 2012 either. Which is still officially supported by Storj.
And will require Window 10 / Server 2016 as a very minimum to run.
Because storj start to built from source code using new version of the Go programming language (1.22 it seems ci: bump Go builds to 1.22.2 · storj/storj@14cfbf3 · GitHub, where the breaking point is Go ver >=1.21.5 ), in which compatibility with many old operating systems was completely (and it seems very intentionally) broken. Because even smallest and simplest programs like the output of a single line of text like classic “Hello world!” produce same fatal errors right after start if built with Go ver >=1.21.5: runtime: Applications will not launch in Windows 7 · Issue #64622 · golang/go · GitHub
Same apply to old MacOS versions and not limited to Windows:
As announced in the Go 1.20 release notes, Go 1.21 requires macOS 10.15 Catalina or later; support for previous versions has been discontinued.
Go 1.20 is the last release that will run on macOS 10.13 High Sierra or 10.14 Mojave. Go 1.21 will require macOS 10.15 Catalina or later.
Perhaps this will cause additional large delays with the deployment of storagenode v 1.107+. Because devs will see an increased % of the nodes crash/going offline when updating to it. In fact, it looks like the rollout of updates to v.107 has already been suspended - the position of the “cursor” has not changed for several days.
Perhaps the developers have not yet figured out what the problem is and are looking for a reasons. Well, the hint to one of the reasons is above.