-
If a pre-release user chooses to not receive pre-release updates (from settings), checking for update shouldn't alert them of an update unless it's a newer build. I'm on 22000.434.41.11 EDIT: Just to be clear: I updated to the pre-release just now (22000.434.41.11) and it is alerting me of an update, pointing me to (22000.376.40.21). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
This has been discussed before. Version numbers are meaningless for the updater, they’re only there for humans to kind of keep track. As you have seen, there may be different builds with the same version. If the updater sees a different hash for the remote file compared to the local file, it deems it an update and that’s it. Also, pre-releases are for enthusiasts. The hope is that people use these, identify problems and help solve them in the upstream, working towards a stable, bug free pre-release that becomes a release. For such an use case, there is no need to go back to a previous release. |
Beta Was this translation helpful? Give feedback.
This has been discussed before. Version numbers are meaningless for the updater, they’re only there for humans to kind of keep track. As you have seen, there may be different builds with the same version. If the updater sees a different hash for the remote file compared to the local file, it deems it an update and that’s it.
Also, pre-releases are for enthusiasts. The hope is that people use these, identify problems and help solve them in the upstream, working towards a stable, bug free pre-release that becomes a release. For such an use case, there is no need to go back to a previous release.