brave update: willDownloadUpdate with AppcastItem(Date: Sun, 08:57:00 +0000, Version: 1.39.111.0) brave update: did find valid update with AppcastItem(Date: Sun, 08:57:00 +0000, Version: 1.39.111.0)
Expect the version you have received to be lower than the first version of Brave that is based on Chromium 104+. If you do receive a new version via auto-updates this way, make sure that Brave can still be launched after. Once Brave is based on Chromium 104+, download an old version of Brave on macOS 10.11 or 10.12.
Test that newly unsupported macOS versions don't receive the update See for example the section "Test Plan" in brave/brave-core#12335. The existing update functionality (in the background and on-demand via brave://settings/help) should not be affected on supported macOS versions. It should be automatically computed from Chromium's minimum declared macOS version. We want to set this attribute on all our new versions. The solution is use Sparkle's minimumSystemVersion attribute to specify the minimum macOS version our updates require. The goal of this issue is to avoid this this time. When this happened the last time, users on the previously highest macOS version received a new version of Brave that was incompatible with their system. This means that also we will drop support for these versions.
Soon (M104), new versions of Chromium will drop support for macOS 10.11 and 10.12. At the moment, Brave's minimum supported macOS version is 10.11.
0 kommentar(er)
